Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93f49c6b32bb020fdee0e54fe553499e94ee893e1cfd8452c0959bdd2d2fdf5e

Tx prefix hash: f749075a1fb53585377ad23fa44354b9ac7b95b853398b2379a9731dd619b9d4
Tx public key: c76733821d49215ca795b935ac8a89a8fbadffbbf6178b63d928f751aac083c4
Timestamp: 1719357089 Timestamp [UCT]: 2024-06-25 23:11:29 Age [y:d:h:m:s]: 00:264:13:18:55
Block: 1052214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189055 RingCT/type: yes/0
Extra: 01c76733821d49215ca795b935ac8a89a8fbadffbbf6178b63d928f751aac083c40211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7dcb4662a2949b017bd6211b9a8dc0a8a7014668f61c54c9a25be8b684f9bdae 0.600000000000 1522537 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": 1052224, "vin": [ { "gen": { "height": 1052214 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7dcb4662a2949b017bd6211b9a8dc0a8a7014668f61c54c9a25be8b684f9bdae" } } ], "extra": [ 1, 199, 103, 51, 130, 29, 73, 33, 92, 167, 149, 185, 53, 172, 138, 137, 168, 251, 173, 255, 187, 246, 23, 139, 99, 217, 40, 247, 81, 170, 192, 131, 196, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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