Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9a5a7785057365def2f736325edf3368e839dde1a80b9abec26ffef7b38a702

Tx prefix hash: 6b04bd62b6ddf79d0b4f825fbac430f880e6f8c00c5de620ba0d1f0113e57d94
Tx public key: ad9bbd3b62049a338932ef08f8296f1bb7400e291ae4ca20d7755b8e6ef2ad15
Timestamp: 1739016262 Timestamp [UTC]: 2025-02-08 12:04:22 Age [y:d:h:m:s]: 01:282:02:57:04
Block: 1214777 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 465679 RingCT/type: yes/0
Extra: 01ad9bbd3b62049a338932ef08f8296f1bb7400e291ae4ca20d7755b8e6ef2ad15021100000003007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bdb12832c3aac272a33e47374ec9073a4caf9aa4e135ba552577e10a5f9f7303 0.000600000000 1701572 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": 1214787, "vin": [ { "gen": { "height": 1214777 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bdb12832c3aac272a33e47374ec9073a4caf9aa4e135ba552577e10a5f9f7303" } } ], "extra": [ 1, 173, 155, 189, 59, 98, 4, 154, 51, 137, 50, 239, 8, 248, 41, 111, 27, 183, 64, 14, 41, 26, 228, 202, 32, 215, 117, 91, 142, 110, 242, 173, 21, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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: