Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e945e13e8e93fe143768fa9782fd0cd85fb71e59ffe0fb92047a8c83c01caa61

Tx prefix hash: 889bbf11dc666686abb210c6633fa1f34dd36e1872813c222582dbf18ab19b68
Tx public key: a2dd9f85c4a8c6a5e8dc96cdbbf5369f8d52d394ed65b783cb16f02e27569cdb
Timestamp: 1703608098 Timestamp [UCT]: 2023-12-26 16:28:18 Age [y:d:h:m:s]: 01:318:10:21:25
Block: 921661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 486411 RingCT/type: yes/0
Extra: 01a2dd9f85c4a8c6a5e8dc96cdbbf5369f8d52d394ed65b783cb16f02e27569cdb02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3010615f33850f62f8b3861d5e7b6db754d9b9da8167da9112cea4f7d74101e 0.600000000000 1379351 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": 921671, "vin": [ { "gen": { "height": 921661 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3010615f33850f62f8b3861d5e7b6db754d9b9da8167da9112cea4f7d74101e" } } ], "extra": [ 1, 162, 221, 159, 133, 196, 168, 198, 165, 232, 220, 150, 205, 187, 245, 54, 159, 141, 82, 211, 148, 237, 101, 183, 131, 203, 22, 240, 46, 39, 86, 156, 219, 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