Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed6e5cc7a0045bd02d53c741f1197b9b1050f77cf5939e6e934cd7e1174903ff

Tx prefix hash: 3ea5e204571a80ffd2c8a7f586cfdc9cabaf0c27021a69787994929e9a7cf9a2
Tx public key: 603aa2cf8eb2343a8590ba5dfe5476083a589bedd408ec54dc56a20a1d5c9b01
Timestamp: 1648917533 Timestamp [UCT]: 2022-04-02 16:38:53 Age [y:d:h:m:s]: 02:181:08:47:40
Block: 471749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 649309 RingCT/type: yes/0
Extra: 01603aa2cf8eb2343a8590ba5dfe5476083a589bedd408ec54dc56a20a1d5c9b0102110000000c37cb3088000000000000000000

1 output(s) for total of 16.784174171000 dcy

stealth address amount amount idx
00: ce39cc44c173a015b290d7bbdd198547e032f4ba0cddd3deee3c559072a65d84 16.784174171000 891143 of 0

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": 471759, "vin": [ { "gen": { "height": 471749 } } ], "vout": [ { "amount": 16784174171, "target": { "key": "ce39cc44c173a015b290d7bbdd198547e032f4ba0cddd3deee3c559072a65d84" } } ], "extra": [ 1, 96, 58, 162, 207, 142, 178, 52, 58, 133, 144, 186, 93, 254, 84, 118, 8, 58, 88, 155, 237, 212, 8, 236, 84, 220, 86, 162, 10, 29, 92, 155, 1, 2, 17, 0, 0, 0, 12, 55, 203, 48, 136, 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