Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e0854aa84c4404ef1ffaf21576adf4b9b41518789a3211c922084064dc05d93

Tx prefix hash: 3a97bd66a7a80317e7d691bbbb4817516924b4bfae6c1dd9c10bf8d2a9569906
Tx public key: a09cad9e0eb5e11afa02ff447e8c8b169226bd4187100ef188975f27e12ca58e
Timestamp: 1676631200 Timestamp [UCT]: 2023-02-17 10:53:20 Age [y:d:h:m:s]: 02:323:15:21:44
Block: 698890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 750699 RingCT/type: yes/0
Extra: 01a09cad9e0eb5e11afa02ff447e8c8b169226bd4187100ef188975f27e12ca58e021100000003faf35c9c000000000000000000

1 output(s) for total of 2.966792838000 dcy

stealth address amount amount idx
00: 99fa02d6efd9e39d6dc06db274fa1c97adfceceafb30a5cbb09402f46f45ccde 2.966792838000 1142269 of 0

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": 698900, "vin": [ { "gen": { "height": 698890 } } ], "vout": [ { "amount": 2966792838, "target": { "key": "99fa02d6efd9e39d6dc06db274fa1c97adfceceafb30a5cbb09402f46f45ccde" } } ], "extra": [ 1, 160, 156, 173, 158, 14, 181, 225, 26, 250, 2, 255, 68, 126, 140, 139, 22, 146, 38, 189, 65, 135, 16, 14, 241, 136, 151, 95, 39, 225, 44, 165, 142, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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