Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d79e3e418566b160ca53adf5bfb907f105e50c6459480a3e995fe71acf9a4187

Tx prefix hash: cb471ea6b9fd9bf7943d8d532dcce407361d3793d5afb67af7725ee766f68b15
Tx public key: c884102cb3cf35914a2db32b5f02b5b9f848d4457d4c22a0668bf957da13c02b
Timestamp: 1736436093 Timestamp [UCT]: 2025-01-09 15:21:33 Age [y:d:h:m:s]: 00:302:11:49:28
Block: 1193679 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213694 RingCT/type: yes/0
Extra: 01c884102cb3cf35914a2db32b5f02b5b9f848d4457d4c22a0668bf957da13c02b0211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e07c44c0714bf5b34a4bded3eec63bc23b1a06ec559f8bd347620b4c9441803 0.600000000000 1680242 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": 1193689, "vin": [ { "gen": { "height": 1193679 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e07c44c0714bf5b34a4bded3eec63bc23b1a06ec559f8bd347620b4c9441803" } } ], "extra": [ 1, 200, 132, 16, 44, 179, 207, 53, 145, 74, 45, 179, 43, 95, 2, 181, 185, 248, 72, 212, 69, 125, 76, 34, 160, 102, 139, 249, 87, 218, 19, 192, 43, 2, 17, 0, 0, 0, 9, 31, 10, 83, 235, 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