Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7e86b489112d997e6f4291bf552501e25c6856a4e479caa9c201d578e9eb4b6

Tx prefix hash: 23a2c969c85d220377afcc5a83d5342ef05ace937c7963b1f1e7fbe53e97baa3
Tx public key: e649c4eb299cb9883db2a21d4fd326cdd421cf8b853f4e03d059632054fa49cf
Timestamp: 1750135548 Timestamp [UCT]: 2025-06-17 04:45:48 Age [y:d:h:m:s]: 00:156:17:14:29
Block: 1306712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109806 RingCT/type: yes/0
Extra: 01e649c4eb299cb9883db2a21d4fd326cdd421cf8b853f4e03d059632054fa49cf021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66af3887e9afd28851410a5a449d74eb4d6a13fd03ff086346eadbc62e3c06a4 0.600000000000 1794319 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": 1306722, "vin": [ { "gen": { "height": 1306712 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66af3887e9afd28851410a5a449d74eb4d6a13fd03ff086346eadbc62e3c06a4" } } ], "extra": [ 1, 230, 73, 196, 235, 41, 156, 185, 136, 61, 178, 162, 29, 79, 211, 38, 205, 212, 33, 207, 139, 133, 63, 78, 3, 208, 89, 99, 32, 84, 250, 73, 207, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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