Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76e96ccb66aeafdaf350b812f075e57c583989b3e4105e57854eeb38cdab70f3

Tx prefix hash: 7e8b46fe5899cf359e7385f1690bd896b136b664a1c9f599ba027f369b6a2a6c
Tx public key: 50addc7fe6c7eb5ac1623b08de4c79eb1607cea102c8d953d44514ed09673a4e
Timestamp: 1762763448 Timestamp [UCT]: 2025-11-10 08:30:48 Age [y:d:h:m:s]: 00:081:11:57:42
Block: 1408965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58167 RingCT/type: yes/0
Extra: 0150addc7fe6c7eb5ac1623b08de4c79eb1607cea102c8d953d44514ed09673a4e02110000000fdf5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b30ba41c236e2ed2f83994626e5236d46bdfad969c3695e2f3397c0d9159b603 0.600000000000 1897396 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": 1408975, "vin": [ { "gen": { "height": 1408965 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b30ba41c236e2ed2f83994626e5236d46bdfad969c3695e2f3397c0d9159b603" } } ], "extra": [ 1, 80, 173, 220, 127, 230, 199, 235, 90, 193, 98, 59, 8, 222, 76, 121, 235, 22, 7, 206, 161, 2, 200, 217, 83, 212, 69, 20, 237, 9, 103, 58, 78, 2, 17, 0, 0, 0, 15, 223, 90, 36, 122, 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