Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34ef0717952fa21f3b90b218a67f68e1d20e14abf564caf40df603d7c30b2f1e

Tx prefix hash: 92567d9a17a27f5586d972363a52e7f4336da8c3dc3133f170d0b0b9c9b12fe6
Tx public key: 2578a7b548ca8192ebdc3fbfcc0fb25ebe08ab36f8de7a42c2bc85a00892bd9c
Timestamp: 1762787610 Timestamp [UCT]: 2025-11-10 15:13:30 Age [y:d:h:m:s]: 00:054:13:46:47
Block: 1409161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39084 RingCT/type: yes/0
Extra: 012578a7b548ca8192ebdc3fbfcc0fb25ebe08ab36f8de7a42c2bc85a00892bd9c02110000001070609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06c2dae13a82bd4f92f3aabe3cbdd2726c48e4edbab9c866d2016fb57361d20c 0.600000000000 1897594 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": 1409171, "vin": [ { "gen": { "height": 1409161 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06c2dae13a82bd4f92f3aabe3cbdd2726c48e4edbab9c866d2016fb57361d20c" } } ], "extra": [ 1, 37, 120, 167, 181, 72, 202, 129, 146, 235, 220, 63, 191, 204, 15, 178, 94, 190, 8, 171, 54, 248, 222, 122, 66, 194, 188, 133, 160, 8, 146, 189, 156, 2, 17, 0, 0, 0, 16, 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