Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: cd8b8a535ae896b8afad6e07ceabf26e2e844d1f07a542a0b9ea709ba542cbab

Tx prefix hash: 259f07ac6ad7b3a4c9abb27657efba79e33834f4ff448a6adc1c8a295b893ed6
Tx public key: 9c5370ef4c574b413b420cfdc14525c63aa550add035aa5e999f400985d60af9
Timestamp: 1702302786 Timestamp [UCT]: 2023-12-11 13:53:06 Age [y:d:h:m:s]: 01:133:08:12:11
Block: 910834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356443 RingCT/type: yes/0
Extra: 019c5370ef4c574b413b420cfdc14525c63aa550add035aa5e999f400985d60af9021100000011e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9ff61ba15a2de4292513985edf2eb9f16b26922fb450c1ef84b28ed6d021248 0.600000000000 1368007 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 910844, "vin": [ { "gen": { "height": 910834 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9ff61ba15a2de4292513985edf2eb9f16b26922fb450c1ef84b28ed6d021248" } } ], "extra": [ 1, 156, 83, 112, 239, 76, 87, 75, 65, 59, 66, 12, 253, 193, 69, 37, 198, 58, 165, 80, 173, 208, 53, 170, 94, 153, 159, 64, 9, 133, 214, 10, 249, 2, 17, 0, 0, 0, 17, 230, 210, 127, 156, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8