Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80f42ae12710a99d774864815ce4bba815a71b1ae4e0dad61de428587275ea17

Tx prefix hash: 1282147ae0470e4d761ae55a8953875f7b17681ceba4a2bc786c43f229b540a5
Tx public key: 1a21acf555dec7584a1dbc6fade9b4dcbbd5c5a1649ec450c6f642fbba279c3d
Timestamp: 1736995425 Timestamp [UCT]: 2025-01-16 02:43:45 Age [y:d:h:m:s]: 00:153:22:06:03
Block: 1198305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109703 RingCT/type: yes/0
Extra: 011a21acf555dec7584a1dbc6fade9b4dcbbd5c5a1649ec450c6f642fbba279c3d0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e8ef8a68d851cc816ad304e0a6e6f32c765b674dee7b911082599ef1077ef22 0.600000000000 1684928 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": 1198315, "vin": [ { "gen": { "height": 1198305 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e8ef8a68d851cc816ad304e0a6e6f32c765b674dee7b911082599ef1077ef22" } } ], "extra": [ 1, 26, 33, 172, 245, 85, 222, 199, 88, 74, 29, 188, 111, 173, 233, 180, 220, 187, 213, 197, 161, 100, 158, 196, 80, 198, 246, 66, 251, 186, 39, 156, 61, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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