Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac81aa349dd14ea81c6e21462cd1445a4d4e62c6ae2ed538e781fdd7b38c758a

Tx prefix hash: 5b7251b717e8e7d565abfa6df36ade711a2f515bebc70ceb9693ec2a57d15b9b
Tx public key: c8e7e51e2b410c891bcbc45db5307519f93d5e6e8217e94b729834c2dcb88799
Timestamp: 1694401365 Timestamp [UCT]: 2023-09-11 03:02:45 Age [y:d:h:m:s]: 01:130:06:08:49
Block: 845507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354426 RingCT/type: yes/0
Extra: 01c8e7e51e2b410c891bcbc45db5307519f93d5e6e8217e94b729834c2dcb8879902110000000375e3f0e9000000000000000000

1 output(s) for total of 0.969358417000 dcy

stealth address amount amount idx
00: f30b4096e517ac0ad2be5688ec1e9cfefc3b1c8834174526f2b06d379154754e 0.969358417000 1298899 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": 845517, "vin": [ { "gen": { "height": 845507 } } ], "vout": [ { "amount": 969358417, "target": { "key": "f30b4096e517ac0ad2be5688ec1e9cfefc3b1c8834174526f2b06d379154754e" } } ], "extra": [ 1, 200, 231, 229, 30, 43, 65, 12, 137, 27, 203, 196, 93, 181, 48, 117, 25, 249, 61, 94, 110, 130, 23, 233, 75, 114, 152, 52, 194, 220, 184, 135, 153, 2, 17, 0, 0, 0, 3, 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