Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72efcfe19a46d0d1cbda126cfce0a4adb4bf47bb141a3524bc528d28b692ee10

Tx prefix hash: b4554bf4ae7d98617f32b7fc483fefcdb2fe0016a44091a80311604d205896b5
Tx public key: c4c68cd8d103dbb318ac6505cab735c917ae829ec7eee2589a83b323c64def66
Timestamp: 1764496589 Timestamp [UCT]: 2025-11-30 09:56:29 Age [y:d:h:m:s]: 00:022:19:48:13
Block: 1423328 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16332 RingCT/type: yes/0
Extra: 01c4c68cd8d103dbb318ac6505cab735c917ae829ec7eee2589a83b323c64def66021100000001defb8f18000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63e7e2345d4e1d1d258aa3b571a05c17fbbc564a9877a9bc9849e48f26ff281c 0.600000000000 1911935 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": 1423338, "vin": [ { "gen": { "height": 1423328 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63e7e2345d4e1d1d258aa3b571a05c17fbbc564a9877a9bc9849e48f26ff281c" } } ], "extra": [ 1, 196, 198, 140, 216, 209, 3, 219, 179, 24, 172, 101, 5, 202, 183, 53, 201, 23, 174, 130, 158, 199, 238, 226, 88, 154, 131, 179, 35, 198, 77, 239, 102, 2, 17, 0, 0, 0, 1, 222, 251, 143, 24, 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