Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a2413ca6a57b9471465c59eb02e2ee6f072377ebf927d6747de31fdb7bd00b8

Tx prefix hash: 9261c1b780f330f575f452c9e6c590b2b48b65ccc923f10eecf3179fd320ca83
Tx public key: 6d1b2fb6e5103315f1a445b8b8e97d4a01e7a3a59789719a9933a3b0deb04aad
Timestamp: 1717968600 Timestamp [UCT]: 2024-06-09 21:30:00 Age [y:d:h:m:s]: 00:303:15:07:07
Block: 1040711 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216997 RingCT/type: yes/0
Extra: 016d1b2fb6e5103315f1a445b8b8e97d4a01e7a3a59789719a9933a3b0deb04aad0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4a25e1e4a2b3a4a9328cd8605a5a741177051683bb1dcbe947cdf02baa49ffd 0.600000000000 1509370 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": 1040721, "vin": [ { "gen": { "height": 1040711 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4a25e1e4a2b3a4a9328cd8605a5a741177051683bb1dcbe947cdf02baa49ffd" } } ], "extra": [ 1, 109, 27, 47, 182, 229, 16, 51, 21, 241, 164, 69, 184, 184, 233, 125, 74, 1, 231, 163, 165, 151, 137, 113, 154, 153, 51, 163, 176, 222, 176, 74, 173, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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