Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47ccadafdedd452b80425479a8b3d0313df1444eb1cbd35d19c686d80846da94

Tx prefix hash: 59ece54a4ab152ee7c062fadf2fcb7ae66923446bde2b79270dd7905bdff03f6
Tx public key: 9c78d7eb3e8584de4b024d4e7d53730ba2f1f2b1671dd9da24f201754a581391
Timestamp: 1634356334 Timestamp [UCT]: 2021-10-16 03:52:14 Age [y:d:h:m:s]: 03:071:15:02:20
Block: 353988 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 829078 RingCT/type: yes/0
Extra: 019c78d7eb3e8584de4b024d4e7d53730ba2f1f2b1671dd9da24f201754a58139102110000001a8d0de867000000000000000000

1 output(s) for total of 41.219119192000 dcy

stealth address amount amount idx
00: b25c6b0ce65e8c8439fe8aa7cf33422293b1d2a2ac612ae75758f21687c8b625 41.219119192000 723194 of 0

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": 353998, "vin": [ { "gen": { "height": 353988 } } ], "vout": [ { "amount": 41219119192, "target": { "key": "b25c6b0ce65e8c8439fe8aa7cf33422293b1d2a2ac612ae75758f21687c8b625" } } ], "extra": [ 1, 156, 120, 215, 235, 62, 133, 132, 222, 75, 2, 77, 78, 125, 83, 115, 11, 162, 241, 242, 177, 103, 29, 217, 218, 36, 242, 1, 117, 74, 88, 19, 145, 2, 17, 0, 0, 0, 26, 141, 13, 232, 103, 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