Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 479e34e0d497f3ecf6adab739e2fa82f64124e0b683cd45b07d7d18884e06765

Tx prefix hash: c9fd8b017cd3a41670b027fa127b2f3adf1a1ae2ba33191189ee08b2828f5014
Tx public key: 505038f310356a0aacdb842996fc360ce20fb506d8d3779d9c5932d8898ebc57
Timestamp: 1764866447 Timestamp [UTC]: 2025-12-04 16:40:47 Age [y:d:h:m:s]: 00:352:15:31:51
Block: 1426412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257082 RingCT/type: yes/0
Extra: 01505038f310356a0aacdb842996fc360ce20fb506d8d3779d9c5932d8898ebc5702110000000cd6e19d7c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3e648e606342578b54f9a276cd8ef2a29a9e8b3b9040cc23bb3135fa88d85f63 0.000600000000 1915103 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": 1426422, "vin": [ { "gen": { "height": 1426412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e648e606342578b54f9a276cd8ef2a29a9e8b3b9040cc23bb3135fa88d85f63" } } ], "extra": [ 1, 80, 80, 56, 243, 16, 53, 106, 10, 172, 219, 132, 41, 150, 252, 54, 12, 226, 15, 181, 6, 216, 211, 119, 157, 156, 89, 50, 216, 137, 142, 188, 87, 2, 17, 0, 0, 0, 12, 214, 225, 157, 124, 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: