Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29592eb89ef2553768f501ccad40dff26da2e7027abe40f6594f27f7fbc8d664

Tx prefix hash: e521729b3024e8b21ff41e1e4a16445e0d059c63227b14f6fb0ea41463700258
Tx public key: a1dee9fd0e15d0834701de9f90a1f8c28f583d4919a7e870c869e1cab6a3668d
Timestamp: 1746814854 Timestamp [UCT]: 2025-05-09 18:20:54 Age [y:d:h:m:s]: 00:192:14:56:45
Block: 1279333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135381 RingCT/type: yes/0
Extra: 01a1dee9fd0e15d0834701de9f90a1f8c28f583d4919a7e870c869e1cab6a3668d0211000000019f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7246f51074a8847f83561530ee6d02b5641ce608c712fe1ad6e53deac60437f1 0.600000000000 1766708 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": 1279343, "vin": [ { "gen": { "height": 1279333 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7246f51074a8847f83561530ee6d02b5641ce608c712fe1ad6e53deac60437f1" } } ], "extra": [ 1, 161, 222, 233, 253, 14, 21, 208, 131, 71, 1, 222, 159, 144, 161, 248, 194, 143, 88, 61, 73, 25, 167, 232, 112, 200, 105, 225, 202, 182, 163, 102, 141, 2, 17, 0, 0, 0, 1, 159, 159, 230, 140, 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