Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e6aced86de427bb1578099d51d4cd4c644e04674f86f7de53aec842ed6d7500

Tx prefix hash: d3597d720d1dc8c36ee5b3283231948c3d9cb938bf47eb927713b656b8917ad3
Tx public key: fb00009feea5369853fc3da6d190e94ea7fb0f8d88e59097d26ea82cedca4a93
Timestamp: 1749915651 Timestamp [UCT]: 2025-06-14 15:40:51 Age [y:d:h:m:s]: 00:159:03:17:29
Block: 1304927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111503 RingCT/type: yes/0
Extra: 01fb00009feea5369853fc3da6d190e94ea7fb0f8d88e59097d26ea82cedca4a93021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b893a4a50d744256df33aae5df0cda66c373c5a8a80351f59bc261922d3d156 0.600000000000 1792522 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": 1304937, "vin": [ { "gen": { "height": 1304927 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b893a4a50d744256df33aae5df0cda66c373c5a8a80351f59bc261922d3d156" } } ], "extra": [ 1, 251, 0, 0, 159, 238, 165, 54, 152, 83, 252, 61, 166, 209, 144, 233, 78, 167, 251, 15, 141, 136, 229, 144, 151, 210, 110, 168, 44, 237, 202, 74, 147, 2, 17, 0, 0, 0, 2, 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