Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9d13e9e749c3958fa1b3894196d63a6c204b524cb1dfc4c72e93e6c94869a98

Tx prefix hash: 2f7269454b323be6453bb757ad1802ed4f0fca710869b8deca3acd1a2c4403cc
Tx public key: 59277c0ee3ea8fed2aabc956b50e9b8b76134f48139700b6efec5f81e2c78db8
Timestamp: 1757932330 Timestamp [UCT]: 2025-09-15 10:32:10 Age [y:d:h:m:s]: 00:115:09:10:56
Block: 1368920 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82630 RingCT/type: yes/0
Extra: 0159277c0ee3ea8fed2aabc956b50e9b8b76134f48139700b6efec5f81e2c78db8021100000003b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a248909316b185cb77dc83c318371d1f362c51d4c54a018934336c8710898f79 0.600000000000 1856975 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": 1368930, "vin": [ { "gen": { "height": 1368920 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a248909316b185cb77dc83c318371d1f362c51d4c54a018934336c8710898f79" } } ], "extra": [ 1, 89, 39, 124, 14, 227, 234, 143, 237, 42, 171, 201, 86, 181, 14, 155, 139, 118, 19, 79, 72, 19, 151, 0, 182, 239, 236, 95, 129, 226, 199, 141, 184, 2, 17, 0, 0, 0, 3, 178, 247, 132, 196, 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