Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f996732d0f9a5ed85f644ddafb1f6d6cda325af1383a0bc48468d3fb4853c2f

Tx prefix hash: 045d4229b5f2c89133655accff302d233796e316491a95820a68278a949e90a1
Tx public key: ca2332e024fab9c10be761360d62cb09a89b377c139c4a136835c7f8610827d6
Timestamp: 1742827190 Timestamp [UTC]: 2025-03-24 14:39:50 Age [y:d:h:m:s]: 01:242:12:30:47
Block: 1246321 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 437173 RingCT/type: yes/0
Extra: 01ca2332e024fab9c10be761360d62cb09a89b377c139c4a136835c7f8610827d6021100000001c6740958000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d3f4b7c98d424dc23b4394c683c85c83f616c1ef8e274973db3e5aa5c28f421e 0.000600000000 1733322 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": 1246331, "vin": [ { "gen": { "height": 1246321 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3f4b7c98d424dc23b4394c683c85c83f616c1ef8e274973db3e5aa5c28f421e" } } ], "extra": [ 1, 202, 35, 50, 224, 36, 250, 185, 193, 11, 231, 97, 54, 13, 98, 203, 9, 168, 155, 55, 124, 19, 156, 74, 19, 104, 53, 199, 248, 97, 8, 39, 214, 2, 17, 0, 0, 0, 1, 198, 116, 9, 88, 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: