Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 297a0f2f6af80b251ebf0011f64e52fdd34631038f746bba56584d2bf1c4e5dc

Tx prefix hash: 3f822b2684f9b29992a9be920b36c89f22e8fe1f866d620140946f15444e6ee1
Tx public key: d3c4e4f6ef52ae62066899bf347bbd2a077e1bc5bd541ac0d43c8ea5fb22d154
Timestamp: 1758160363 Timestamp [UTC]: 2025-09-18 01:52:43 Age [y:d:h:m:s]: 01:056:06:08:02
Block: 1370805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306444 RingCT/type: yes/0
Extra: 01d3c4e4f6ef52ae62066899bf347bbd2a077e1bc5bd541ac0d43c8ea5fb22d154021100000001b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3506669315f8005872ee4dc8351ad034a872774dd9fb9feb26fa2aaba058a13c 0.000600000000 1858882 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": 1370815, "vin": [ { "gen": { "height": 1370805 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3506669315f8005872ee4dc8351ad034a872774dd9fb9feb26fa2aaba058a13c" } } ], "extra": [ 1, 211, 196, 228, 246, 239, 82, 174, 98, 6, 104, 153, 191, 52, 123, 189, 42, 7, 126, 27, 197, 189, 84, 26, 192, 212, 60, 142, 165, 251, 34, 209, 84, 2, 17, 0, 0, 0, 1, 178, 247, 132, 196, 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: