Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5b338342dbadd60fbda72c8c41fbeb39ddd390a2f8d35318eb086771e3bb556

Tx prefix hash: 254fd27c85857eaeab78c7dfd3e551767f9a2ff895d355b0c96e90b098079662
Tx public key: f9fa47adcaf2ad955357257b9d3be60ff8351fbbc970f4c748099d9aa71bc1d3
Timestamp: 1704418803 Timestamp [UCT]: 2024-01-05 01:40:03 Age [y:d:h:m:s]: 01:086:12:10:15
Block: 928354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322945 RingCT/type: yes/0
Extra: 01f9fa47adcaf2ad955357257b9d3be60ff8351fbbc970f4c748099d9aa71bc1d302110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3acf06586c5cba7cad610e443a7fe9d2e898c2a509809ca2a207cb4e77611d3 0.600000000000 1386212 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": 928364, "vin": [ { "gen": { "height": 928354 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3acf06586c5cba7cad610e443a7fe9d2e898c2a509809ca2a207cb4e77611d3" } } ], "extra": [ 1, 249, 250, 71, 173, 202, 242, 173, 149, 83, 87, 37, 123, 157, 59, 230, 15, 248, 53, 31, 187, 201, 112, 244, 199, 72, 9, 157, 154, 167, 27, 193, 211, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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