Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 439f7bbf6264e79f58d5cc7721cd1b1d8582564d97b0d590021cb198c57b931f

Tx prefix hash: 0224f6fe1bc15e3a258b94bc9b562f20ad5ddbc99565e68d4df8e0c207f7b798
Tx public key: 56016287b9658bc8a5bca1e41c5d9d536f7c708f990f0a2e2db8731444596927
Timestamp: 1764502516 Timestamp [UCT]: 2025-11-30 11:35:16 Age [y:d:h:m:s]: 00:062:05:23:04
Block: 1423382 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 44367 RingCT/type: yes/0
Extra: 0156016287b9658bc8a5bca1e41c5d9d536f7c708f990f0a2e2db8731444596927021100000005d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5892eec0206b5b0476d7474beba5beceb6480bed14c35d61599054204aa268ae 0.600000000000 1911991 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": 1423392, "vin": [ { "gen": { "height": 1423382 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5892eec0206b5b0476d7474beba5beceb6480bed14c35d61599054204aa268ae" } } ], "extra": [ 1, 86, 1, 98, 135, 185, 101, 139, 200, 165, 188, 161, 228, 28, 93, 157, 83, 111, 124, 112, 143, 153, 15, 10, 46, 45, 184, 115, 20, 68, 89, 105, 39, 2, 17, 0, 0, 0, 5, 214, 225, 157, 124, 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