Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07242e8d006903c327e9d60a30ead58ff58b038cf6fc4bf5ee127897fbb87ba7

Tx prefix hash: 8b8fbb1f3a9b5f3c0580e5469b4619ed0bcdb629621c18e6373d8d544905aace
Tx public key: 28b4ad4a6b1360023572bfcbaee1f1ecb87ec17e13dca37a0dd4759b1348b1e6
Timestamp: 1713643904 Timestamp [UCT]: 2024-04-20 20:11:44 Age [y:d:h:m:s]: 01:194:22:31:53
Block: 1004854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397979 RingCT/type: yes/0
Extra: 0128b4ad4a6b1360023572bfcbaee1f1ecb87ec17e13dca37a0dd4759b1348b1e602110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cdae76506e9755bbdb137e0e07bb02b4f56ee493e3ba13fd884597078360f449 0.600000000000 1465428 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": 1004864, "vin": [ { "gen": { "height": 1004854 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cdae76506e9755bbdb137e0e07bb02b4f56ee493e3ba13fd884597078360f449" } } ], "extra": [ 1, 40, 180, 173, 74, 107, 19, 96, 2, 53, 114, 191, 203, 174, 225, 241, 236, 184, 126, 193, 126, 19, 220, 163, 122, 13, 212, 117, 155, 19, 72, 177, 230, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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