Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6afda63732babcc333209f66d8021aae455e5c110ba1b78943a8beabf494a5a6

Tx prefix hash: 4d0150ff9052a3247cc755ab57e71c92420a047246eb36533b3d9831f61e8197
Tx public key: 73b358c3fd75164f6e0e952a7863546370e82350b7c930a3ddd6b67171a9df5c
Timestamp: 1717899753 Timestamp [UCT]: 2024-06-09 02:22:33 Age [y:d:h:m:s]: 00:283:08:55:25
Block: 1040146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202523 RingCT/type: yes/0
Extra: 0173b358c3fd75164f6e0e952a7863546370e82350b7c930a3ddd6b67171a9df5c021100000004d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e808316e964f91ae2dccdcb64e4eaaf3dc6a13c301ad3b4d2087a23e76543588 0.600000000000 1508803 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": 1040156, "vin": [ { "gen": { "height": 1040146 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e808316e964f91ae2dccdcb64e4eaaf3dc6a13c301ad3b4d2087a23e76543588" } } ], "extra": [ 1, 115, 179, 88, 195, 253, 117, 22, 79, 110, 14, 149, 42, 120, 99, 84, 99, 112, 232, 35, 80, 183, 201, 48, 163, 221, 214, 182, 113, 113, 169, 223, 92, 2, 17, 0, 0, 0, 4, 215, 73, 245, 17, 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