Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 229264d651d884f1b6d8f2cc4e4723e3b21bc41f255d48841001df68b738f03a

Tx prefix hash: fd0398dbe7cdbaa949a5846b9528739e73dc38e35a0a136dfc4829e7317dd890
Tx public key: fdbcc1227b5706f33fb1fcc83f6ada66fc3c3eb9dd4b08c07922d62a6ca8bc42
Timestamp: 1760117406 Timestamp [UTC]: 2025-10-10 17:30:06 Age [y:d:h:m:s]: 01:042:05:46:14
Block: 1387030 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296464 RingCT/type: yes/0
Extra: 01fdbcc1227b5706f33fb1fcc83f6ada66fc3c3eb9dd4b08c07922d62a6ca8bc4202110000000101491f88000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f971331d63825d197ceb428f30f5765aee1e4be5c66d8df52158aec550001383 0.000600000000 1875215 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": 1387040, "vin": [ { "gen": { "height": 1387030 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f971331d63825d197ceb428f30f5765aee1e4be5c66d8df52158aec550001383" } } ], "extra": [ 1, 253, 188, 193, 34, 123, 87, 6, 243, 63, 177, 252, 200, 63, 106, 218, 102, 252, 60, 62, 185, 221, 75, 8, 192, 121, 34, 214, 42, 108, 168, 188, 66, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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: