Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0895412144226c65a5ba586a1fef5c033f92a229812afce123445d121e7b9c8e

Tx prefix hash: 31c729d3f65bba181d4628fb9152d4340854a18ddc8d9070f272ce02fa0885c4
Tx public key: d5502da6bf85e1d97b170e8690c63f99099da69b02810c8eac8ef5ae4a0f309e
Timestamp: 1685101019 Timestamp [UCT]: 2023-05-26 11:36:59 Age [y:d:h:m:s]: 02:008:14:29:11
Block: 768479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 528268 RingCT/type: yes/0
Extra: 01d5502da6bf85e1d97b170e8690c63f99099da69b02810c8eac8ef5ae4a0f309e02110000000175e3f0e9000000000000000000

1 output(s) for total of 1.744657727000 dcy

stealth address amount amount idx
00: ae68d9e13c7b8799ac4b55a5b11e1c4b9dd7043a29dc5ebf1e2b9a0612f7d4fe 1.744657727000 1217680 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": 768489, "vin": [ { "gen": { "height": 768479 } } ], "vout": [ { "amount": 1744657727, "target": { "key": "ae68d9e13c7b8799ac4b55a5b11e1c4b9dd7043a29dc5ebf1e2b9a0612f7d4fe" } } ], "extra": [ 1, 213, 80, 45, 166, 191, 133, 225, 217, 123, 23, 14, 134, 144, 198, 63, 153, 9, 157, 166, 155, 2, 129, 12, 142, 172, 142, 245, 174, 74, 15, 48, 158, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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