Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a561900d349c5c44390d89f7afe8f7593a50f2bb71ed57af01b8a90df698ed38

Tx prefix hash: 2896801dc063bcf36ca6eaf35fbf3a4df3462fd10458120a0cfef0fde85da431
Tx public key: a447b8ecf8a73b90c31063b97b50fdee651882238eeb9a19ca21724bd0e564c9
Timestamp: 1584772711 Timestamp [UCT]: 2020-03-21 06:38:31 Age [y:d:h:m:s]: 05:229:08:16:04
Block: 86410 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1318445 RingCT/type: yes/0
Extra: 01a447b8ecf8a73b90c31063b97b50fdee651882238eeb9a19ca21724bd0e564c9021100000001e5e30634000000000000000000

1 output(s) for total of 317.468644321000 dcy

stealth address amount amount idx
00: f38009e7d1336d323a020d25c7a93e21d7c3812f041397dd6135308e40c18e48 317.468644321000 155864 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": 86420, "vin": [ { "gen": { "height": 86410 } } ], "vout": [ { "amount": 317468644321, "target": { "key": "f38009e7d1336d323a020d25c7a93e21d7c3812f041397dd6135308e40c18e48" } } ], "extra": [ 1, 164, 71, 184, 236, 248, 167, 59, 144, 195, 16, 99, 185, 123, 80, 253, 238, 101, 24, 130, 35, 142, 235, 154, 25, 202, 33, 114, 75, 208, 229, 100, 201, 2, 17, 0, 0, 0, 1, 229, 227, 6, 52, 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