Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 753bf62bfa4d5e5d305ff9218f9ce2cafcf158051373115b90c3eb2f314b5137

Tx prefix hash: e5e41f94116792d1a4ba4301b8423c167446ccdf15229faab3cb232e74646e18
Tx public key: aa32baef7b2fe8fd2d4754bea580420932a798926e00f37d14f36baa8698d6ca
Timestamp: 1742849457 Timestamp [UTC]: 2025-03-24 20:50:57 Age [y:d:h:m:s]: 01:046:17:07:27
Block: 1246501 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284628 RingCT/type: yes/0
Extra: 01aa32baef7b2fe8fd2d4754bea580420932a798926e00f37d14f36baa8698d6ca02110000000624ff4ea1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 04b5dd77102d089099d9edadb378b373048a6f97c88088abeafc170e53b48a91 0.000600000000 1733502 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": 1246511, "vin": [ { "gen": { "height": 1246501 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04b5dd77102d089099d9edadb378b373048a6f97c88088abeafc170e53b48a91" } } ], "extra": [ 1, 170, 50, 186, 239, 123, 47, 232, 253, 45, 71, 84, 190, 165, 128, 66, 9, 50, 167, 152, 146, 110, 0, 243, 125, 20, 243, 107, 170, 134, 152, 214, 202, 2, 17, 0, 0, 0, 6, 36, 255, 78, 161, 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: