Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb66b6c874336ae064b3937c8312923e2595f290b8de555d3a3e4e85f3e54ae0

Tx prefix hash: e408c967f27ec56f2ddb96b650b5cc8db54018f69291a16537a7fee5bef7564f
Tx public key: 787a316222a47944a41f18bfb3c49170a0e11389945ae32ce6b6e6325c30e54d
Timestamp: 1715245084 Timestamp [UCT]: 2024-05-09 08:58:04 Age [y:d:h:m:s]: 00:314:02:42:03
Block: 1018142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224534 RingCT/type: yes/0
Extra: 01787a316222a47944a41f18bfb3c49170a0e11389945ae32ce6b6e6325c30e54d0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf35aae21a388248ce64fde516b9301e9fd2d72d8e904d67b1216c54f664ae43 0.600000000000 1481929 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": 1018152, "vin": [ { "gen": { "height": 1018142 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf35aae21a388248ce64fde516b9301e9fd2d72d8e904d67b1216c54f664ae43" } } ], "extra": [ 1, 120, 122, 49, 98, 34, 164, 121, 68, 164, 31, 24, 191, 179, 196, 145, 112, 160, 225, 19, 137, 148, 90, 227, 44, 230, 182, 230, 50, 92, 48, 229, 77, 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