Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32d0360f8e8e14895b9b9780e646e786bee06be03257015f73cffe26d033be7a

Tx prefix hash: a0bf37b068da73f492bd0cf97d01c0ca7114bbebd5082e290670982b51534860
Tx public key: dc57b8c4c795974ab71dd83ef3c23058e6940932232b5c7a626d299396b33727
Timestamp: 1747976498 Timestamp [UTC]: 2025-05-23 05:01:38 Age [y:d:h:m:s]: 01:175:18:53:36
Block: 1288966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389528 RingCT/type: yes/0
Extra: 01dc57b8c4c795974ab71dd83ef3c23058e6940932232b5c7a626d299396b33727021100000009a11dba98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6c2b7ec13f19c54fd94e926185bca7d474fb89c630f0cb1ee80bedecf3f7016c 0.000600000000 1776433 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 dinastycoin-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": 1288976, "vin": [ { "gen": { "height": 1288966 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c2b7ec13f19c54fd94e926185bca7d474fb89c630f0cb1ee80bedecf3f7016c" } } ], "extra": [ 1, 220, 87, 184, 196, 199, 149, 151, 74, 183, 29, 216, 62, 243, 194, 48, 88, 230, 148, 9, 50, 35, 43, 92, 122, 98, 109, 41, 147, 150, 179, 55, 39, 2, 17, 0, 0, 0, 9, 161, 29, 186, 152, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: