Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1ac13eb457bbde39f9fae9be32b4001feaf2a7a702a5358aa8ae65b85f79785

Tx prefix hash: f660b08397e021716f2832a3847bbc15d1e1758131a3ca534945d9e5d8d30136
Tx public key: bf3bd0499829427a7f160d0b6669270f19cc8c84ae25255d07586684c5de3d2e
Timestamp: 1699604582 Timestamp [UCT]: 2023-11-10 08:23:02 Age [y:d:h:m:s]: 01:109:06:46:41
Block: 888476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339252 RingCT/type: yes/0
Extra: 01bf3bd0499829427a7f160d0b6669270f19cc8c84ae25255d07586684c5de3d2e021100000008faf35c9c000000000000000000

1 output(s) for total of 0.698409581000 dcy

stealth address amount amount idx
00: 4466ea704fd52ad1c62654ccfc062d68e63b7097776234cf941050c7393f9991 0.698409581000 1344419 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": 888486, "vin": [ { "gen": { "height": 888476 } } ], "vout": [ { "amount": 698409581, "target": { "key": "4466ea704fd52ad1c62654ccfc062d68e63b7097776234cf941050c7393f9991" } } ], "extra": [ 1, 191, 59, 208, 73, 152, 41, 66, 122, 127, 22, 13, 11, 102, 105, 39, 15, 25, 204, 140, 132, 174, 37, 37, 93, 7, 88, 102, 132, 197, 222, 61, 46, 2, 17, 0, 0, 0, 8, 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