Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 564db86d971017de63f027bdd38dc50bf19f1fa1331692962285e7abebd33728

Tx prefix hash: dee6ac3668c40da422e69e34cbea5f5f7495d3965b43968161da9aa9750eb7e2
Tx public key: 49c36ce34b9d386749d55f41199a401d3b8e6fb0e0c9bb5ebc644b68d6afcd4d
Timestamp: 1726518189 Timestamp [UCT]: 2024-09-16 20:23:09 Age [y:d:h:m:s]: 00:261:13:50:10
Block: 1111592 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186829 RingCT/type: yes/0
Extra: 0149c36ce34b9d386749d55f41199a401d3b8e6fb0e0c9bb5ebc644b68d6afcd4d02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7cad4cab5fdb851315b6701f87c3af23d18d42307da85af2202877fb4caa77d 0.600000000000 1590609 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": 1111602, "vin": [ { "gen": { "height": 1111592 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7cad4cab5fdb851315b6701f87c3af23d18d42307da85af2202877fb4caa77d" } } ], "extra": [ 1, 73, 195, 108, 227, 75, 157, 56, 103, 73, 213, 95, 65, 25, 154, 64, 29, 59, 142, 111, 176, 224, 201, 187, 94, 188, 100, 75, 104, 214, 175, 205, 77, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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