Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc0649bf02a6c24ddf07f4f297d0eec2c169e8fa777d805880067b40dbc9d7d6

Tx prefix hash: 4edeb421f8d484ec6dd61bde860f89f8ce94bae5d0c556e67c35876c3d4b128c
Tx public key: d4564986f17dc350ab1568b6120ac5eaea30326408871e21ffdb3d74ea268808
Timestamp: 1761417557 Timestamp [UTC]: 2025-10-25 18:39:17 Age [y:d:h:m:s]: 01:026:10:36:35
Block: 1397815 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285370 RingCT/type: yes/0
Extra: 01d4564986f17dc350ab1568b6120ac5eaea30326408871e21ffdb3d74ea2688080211000000055dfbbe2a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bcdafbe4884404d715c744a3a5477269bf1e9ae07f9019ecc656e055bbb1e0fc 0.000600000000 1886106 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": 1397825, "vin": [ { "gen": { "height": 1397815 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bcdafbe4884404d715c744a3a5477269bf1e9ae07f9019ecc656e055bbb1e0fc" } } ], "extra": [ 1, 212, 86, 73, 134, 241, 125, 195, 80, 171, 21, 104, 182, 18, 10, 197, 234, 234, 48, 50, 100, 8, 135, 30, 33, 255, 219, 61, 116, 234, 38, 136, 8, 2, 17, 0, 0, 0, 5, 93, 251, 190, 42, 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: