Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5f6273c1c29b786b07cc18bd4561a7ce01ac65fc0b61a2d0d12ea8319b8d035

Tx prefix hash: 0ae2989f5a40f32d6863d84bd00794ed16f1862d10970231e7b88f91a87b9449
Tx public key: a0ee39cb60150c30f9e56af8a26deae01678100aa996374f7a2ec45f2c38c1e6
Timestamp: 1745189000 Timestamp [UCT]: 2025-04-20 22:43:20 Age [y:d:h:m:s]: 00:024:09:35:04
Block: 1265858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17472 RingCT/type: yes/0
Extra: 01a0ee39cb60150c30f9e56af8a26deae01678100aa996374f7a2ec45f2c38c1e60211000000016c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c9533cca5c8a6469293c024b81174a4e709d798811b15da02ca0867b1497865 0.600000000000 1753071 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": 1265868, "vin": [ { "gen": { "height": 1265858 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c9533cca5c8a6469293c024b81174a4e709d798811b15da02ca0867b1497865" } } ], "extra": [ 1, 160, 238, 57, 203, 96, 21, 12, 48, 249, 229, 106, 248, 162, 109, 234, 224, 22, 120, 16, 10, 169, 150, 55, 79, 122, 46, 196, 95, 44, 56, 193, 230, 2, 17, 0, 0, 0, 1, 108, 152, 170, 61, 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