Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a44d8962cff5314c80eec8c3946e901b044a846b3d947bd0008b10daaeec0c24

Tx prefix hash: 1f1a845d82c0b13173630c493ded10af49961dc143994f729a6f5ffd58e0df7e
Tx public key: efbf221df07847a972e57f12537eb4ab73f8dd13f896e0b517be6a21c13f5dd1
Timestamp: 1629325767 Timestamp [UCT]: 2021-08-18 22:29:27 Age [y:d:h:m:s]: 03:208:11:15:58
Block: 316711 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 922330 RingCT/type: yes/0
Extra: 01efbf221df07847a972e57f12537eb4ab73f8dd13f896e0b517be6a21c13f5dd102110000001217696b73000000000000000000

1 output(s) for total of 54.777908976000 dcy

stealth address amount amount idx
00: 91453f0b9a9d25cc94e59cce0fdf851a604c07564283d852e2d8da4a33510f46 54.777908976000 658784 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": 316721, "vin": [ { "gen": { "height": 316711 } } ], "vout": [ { "amount": 54777908976, "target": { "key": "91453f0b9a9d25cc94e59cce0fdf851a604c07564283d852e2d8da4a33510f46" } } ], "extra": [ 1, 239, 191, 34, 29, 240, 120, 71, 169, 114, 229, 127, 18, 83, 126, 180, 171, 115, 248, 221, 19, 248, 150, 224, 181, 23, 190, 106, 33, 193, 63, 93, 209, 2, 17, 0, 0, 0, 18, 23, 105, 107, 115, 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