Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96bf960e93725099a8a691a63d2d82c49f0b3a1ca4a0782882f5306999efbbbb

Tx prefix hash: 0025e90a6c9ae258499dc5d1ffc479e154f7215efb02fd5d39033238384a9213
Tx public key: d8af52e5f59be4c7aff8fe5b4b3fb54b60139f76ca6107ed3ba5c00e2f65d5ac
Timestamp: 1737859922 Timestamp [UCT]: 2025-01-26 02:52:02 Age [y:d:h:m:s]: 00:047:09:46:07
Block: 1205419 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33713 RingCT/type: yes/0
Extra: 01d8af52e5f59be4c7aff8fe5b4b3fb54b60139f76ca6107ed3ba5c00e2f65d5ac021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a267638f742e241f55e7bc4b96d5163848391edcad23195c388bb1e19b24461 0.600000000000 1692116 of 15

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": 1205429, "vin": [ { "gen": { "height": 1205419 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a267638f742e241f55e7bc4b96d5163848391edcad23195c388bb1e19b24461" } } ], "extra": [ 1, 216, 175, 82, 229, 245, 155, 228, 199, 175, 248, 254, 91, 75, 63, 181, 75, 96, 19, 159, 118, 202, 97, 7, 237, 59, 165, 192, 14, 47, 101, 213, 172, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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