Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fce4589995a4dc862ed9c02dbee15a97ee3e2e9645674d6f75bd0ea1e51de9f

Tx prefix hash: 0dc995302eaef0098f0b2d43f588e3af9453c89edcec4d041a9e5f4b3fa64e2c
Tx public key: c2825acc24d8a0c627e86afd38d2964007eeb2e7e8a4bef2a13d31229bb297d8
Timestamp: 1764532107 Timestamp [UCT]: 2025-11-30 19:48:27 Age [y:d:h:m:s]: 00:034:20:12:39
Block: 1423625 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24956 RingCT/type: yes/0
Extra: 01c2825acc24d8a0c627e86afd38d2964007eeb2e7e8a4bef2a13d31229bb297d802110000000b70609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2821870076bb2b00d399d5b9d33c25ee7054daa1b82d9509b0a17acc302e287 0.600000000000 1912242 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": 1423635, "vin": [ { "gen": { "height": 1423625 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2821870076bb2b00d399d5b9d33c25ee7054daa1b82d9509b0a17acc302e287" } } ], "extra": [ 1, 194, 130, 90, 204, 36, 216, 160, 198, 39, 232, 106, 253, 56, 210, 150, 64, 7, 238, 178, 231, 232, 164, 190, 242, 161, 61, 49, 34, 155, 178, 151, 216, 2, 17, 0, 0, 0, 11, 112, 96, 157, 3, 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