Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da8abc21baff085bd1aa173a11bbed16ff2b9590b7f1310d09980f6ff9b6fdd3

Tx prefix hash: 553cc63c15d3eecc080caf51372c915a8196b49c3efd2333eca0b70896d7e6e2
Tx public key: 2b66a6c44d5c663dc7a84837a724a716b2d82bf5205f5a766e27e8e9a78b97f9
Timestamp: 1685479165 Timestamp [UCT]: 2023-05-30 20:39:25 Age [y:d:h:m:s]: 01:269:12:50:33
Block: 771612 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 453794 RingCT/type: yes/0
Extra: 012b66a6c44d5c663dc7a84837a724a716b2d82bf5205f5a766e27e8e9a78b97f9021100000002e6d27f9c000000000000000000

1 output(s) for total of 1.703449661000 dcy

stealth address amount amount idx
00: 076a16d16f587705985917aab1e3d6cf1206cfd41a54eb28dbf490fabefc0668 1.703449661000 1220985 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": 771622, "vin": [ { "gen": { "height": 771612 } } ], "vout": [ { "amount": 1703449661, "target": { "key": "076a16d16f587705985917aab1e3d6cf1206cfd41a54eb28dbf490fabefc0668" } } ], "extra": [ 1, 43, 102, 166, 196, 77, 92, 102, 61, 199, 168, 72, 55, 167, 36, 167, 22, 178, 216, 43, 245, 32, 95, 90, 118, 110, 39, 232, 233, 167, 139, 151, 249, 2, 17, 0, 0, 0, 2, 230, 210, 127, 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