Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a1da5157d69f4e99209e737b6475d392f0df0315d3534eb418c6c5a05fa5f0f

Tx prefix hash: 8bfb6fb19c286542d190bbc4a6cd864e3363c1236eb1e32ede5cb5ec2be2be1e
Tx public key: 3257ad5637e18d292256e5ca7b471674ccb12d74cad8ed37a749dac82914452b
Timestamp: 1714232533 Timestamp [UCT]: 2024-04-27 15:42:13 Age [y:d:h:m:s]: 01:277:15:05:31
Block: 1009733 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 456996 RingCT/type: yes/0
Extra: 013257ad5637e18d292256e5ca7b471674ccb12d74cad8ed37a749dac82914452b0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5409afe0d501ef1bac6f9f9b534a175ee45424cda0ac00159a6e0c037036cdc1 0.600000000000 1471489 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": 1009743, "vin": [ { "gen": { "height": 1009733 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5409afe0d501ef1bac6f9f9b534a175ee45424cda0ac00159a6e0c037036cdc1" } } ], "extra": [ 1, 50, 87, 173, 86, 55, 225, 141, 41, 34, 86, 229, 202, 123, 71, 22, 116, 204, 177, 45, 116, 202, 216, 237, 55, 167, 73, 218, 200, 41, 20, 69, 43, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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