Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 281a82d58d76d46215d84f0888255c9c50fb2fff7619c0453939a69e9a9743c0

Tx prefix hash: bae6315b2c5e7b6a6ac06cc10d137c7db9d1995e7199f3b5a193a24a17ff7668
Tx public key: ba9be1c6cb7c3a457ec2058b03de1f620770b097c27f9d6b36ee0cf4d824ca69
Timestamp: 1709474453 Timestamp [UCT]: 2024-03-03 14:00:53 Age [y:d:h:m:s]: 01:074:17:12:26
Block: 970300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314431 RingCT/type: yes/0
Extra: 01ba9be1c6cb7c3a457ec2058b03de1f620770b097c27f9d6b36ee0cf4d824ca6902110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d10c84b195bee8fa26b2a9a853ab0e1a4f13e1df2bee94b82ba0ab0100af2e8a 0.600000000000 1430151 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": 970310, "vin": [ { "gen": { "height": 970300 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d10c84b195bee8fa26b2a9a853ab0e1a4f13e1df2bee94b82ba0ab0100af2e8a" } } ], "extra": [ 1, 186, 155, 225, 198, 203, 124, 58, 69, 126, 194, 5, 139, 3, 222, 31, 98, 7, 112, 176, 151, 194, 127, 157, 107, 54, 238, 12, 244, 216, 36, 202, 105, 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