Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c0577013092639089c68b9966fa9def79aaa83451ccdc2f8def8f906158e89c

Tx prefix hash: 56865277ad46f011400d20fcc5d5d6679ac11beca6c26a63e0ebb6e1431bd14d
Tx public key: d1d0a5d234fcdd843c10dcadf3cbcef3a38693b47ae6d5f739952c8fbd797a60
Timestamp: 1705397820 Timestamp [UCT]: 2024-01-16 09:37:00 Age [y:d:h:m:s]: 00:360:20:18:53
Block: 936480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258352 RingCT/type: yes/0
Extra: 01d1d0a5d234fcdd843c10dcadf3cbcef3a38693b47ae6d5f739952c8fbd797a600211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63e7acc1408d9117be84d450f904912603d882f3befebdebff0d07be6db44bbe 0.600000000000 1394508 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": 936490, "vin": [ { "gen": { "height": 936480 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63e7acc1408d9117be84d450f904912603d882f3befebdebff0d07be6db44bbe" } } ], "extra": [ 1, 209, 208, 165, 210, 52, 252, 221, 132, 60, 16, 220, 173, 243, 203, 206, 243, 163, 134, 147, 180, 122, 230, 213, 247, 57, 149, 44, 143, 189, 121, 122, 96, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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