Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a9e0dde9621d3cf44251feb911048ac6c48c552fc601af535e8ee13b019ebb0

Tx prefix hash: 9ecc1a623aa036375fda8a7381cb86d7510b639afa84a29bc7bcdd35c33a0e92
Tx public key: c5fb9275cca0e85d30c5805a9a7a01c9d93a1ad0bd2804d7dc3431dc10eae6c7
Timestamp: 1704459381 Timestamp [UCT]: 2024-01-05 12:56:21 Age [y:d:h:m:s]: 01:276:20:48:30
Block: 928692 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 456664 RingCT/type: yes/0
Extra: 01c5fb9275cca0e85d30c5805a9a7a01c9d93a1ad0bd2804d7dc3431dc10eae6c702110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e33e6460125deec49d76a503877b66b77c948e9b0c25a6394d6c53192f4bd160 0.600000000000 1386552 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": 928702, "vin": [ { "gen": { "height": 928692 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e33e6460125deec49d76a503877b66b77c948e9b0c25a6394d6c53192f4bd160" } } ], "extra": [ 1, 197, 251, 146, 117, 204, 160, 232, 93, 48, 197, 128, 90, 154, 122, 1, 201, 217, 58, 26, 208, 189, 40, 4, 215, 220, 52, 49, 220, 16, 234, 230, 199, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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