Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c752fdc2e5d0e610f490bfefd80c50c7274ad0ce4196e754aed86eecf81debe5

Tx prefix hash: 43853f71b535740849ac99777e901354c23fb2dc9418fc15441b4ac475e8bb1e
Tx public key: 0ef78e0633ce332876f84529b31dbb033f974c8bf4f2332dad5b20715a4d56f3
Timestamp: 1756590382 Timestamp [UTC]: 2025-08-30 21:46:22 Age [y:d:h:m:s]: 00:293:12:56:00
Block: 1357948 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205829 RingCT/type: yes/0
Extra: 010ef78e0633ce332876f84529b31dbb033f974c8bf4f2332dad5b20715a4d56f3021100000003a11dba98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ed64447c4d9575c4fd18aad6387180e5ef72fe77efc265cb2ebafbabb247b129 0.000600000000 1845957 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": 1357958, "vin": [ { "gen": { "height": 1357948 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed64447c4d9575c4fd18aad6387180e5ef72fe77efc265cb2ebafbabb247b129" } } ], "extra": [ 1, 14, 247, 142, 6, 51, 206, 51, 40, 118, 248, 69, 41, 179, 29, 187, 3, 63, 151, 76, 139, 244, 242, 51, 45, 173, 91, 32, 113, 90, 77, 86, 243, 2, 17, 0, 0, 0, 3, 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: