Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 951444f346b2f56ddd64631d98bb065d4c3a450d6ca45ffeefe141f543f0f489

Tx prefix hash: bffde1c383a1470652b5f7e20c29f0e8f918400d3773570733ee53c22c796c17
Tx public key: df63a0813fb3886c91d1ebd865fa37ef314642778f56bc963ba7f03503b2b292
Timestamp: 1700535811 Timestamp [UCT]: 2023-11-21 03:03:31 Age [y:d:h:m:s]: 01:139:20:21:03
Block: 896181 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361122 RingCT/type: yes/0
Extra: 01df63a0813fb3886c91d1ebd865fa37ef314642778f56bc963ba7f03503b2b29202110000000275e3f0e9000000000000000000

1 output(s) for total of 0.658537201000 dcy

stealth address amount amount idx
00: 0bfc6a1ef977deacab1852bccd397d72b7843c6c40b7b7981d9f2edd3eb3d26c 0.658537201000 1352454 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": 896191, "vin": [ { "gen": { "height": 896181 } } ], "vout": [ { "amount": 658537201, "target": { "key": "0bfc6a1ef977deacab1852bccd397d72b7843c6c40b7b7981d9f2edd3eb3d26c" } } ], "extra": [ 1, 223, 99, 160, 129, 63, 179, 136, 108, 145, 209, 235, 216, 101, 250, 55, 239, 49, 70, 66, 119, 143, 86, 188, 150, 59, 167, 240, 53, 3, 178, 178, 146, 2, 17, 0, 0, 0, 2, 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