Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f61a3fd51b9ef93eef76636fbcc07f3ee4cc37e3ee0e0e922221cad77efd48c

Tx prefix hash: c4aba187a60cc2b9c5d259f8188ab0166806d3260cbe7a06e924c6803527d7d2
Tx public key: 0754e7244abf4bc90b0d3772a7d343df6aec86d2075d552a0ab1ee75ad104084
Timestamp: 1774384347 Timestamp [UTC]: 2026-03-24 20:32:27 Age [y:d:h:m:s]: 00:237:13:24:35
Block: 1505019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175289 RingCT/type: yes/0
Extra: 010754e7244abf4bc90b0d3772a7d343df6aec86d2075d552a0ab1ee75ad104084021100000008f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 798df271a8e56eb789231f5de25f349cea38597ea016fb40acb8d7ddc324c8b6 0.000600000000 1994749 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": 1505029, "vin": [ { "gen": { "height": 1505019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "798df271a8e56eb789231f5de25f349cea38597ea016fb40acb8d7ddc324c8b6" } } ], "extra": [ 1, 7, 84, 231, 36, 74, 191, 75, 201, 11, 13, 55, 114, 167, 211, 67, 223, 106, 236, 134, 210, 7, 93, 85, 42, 10, 177, 238, 117, 173, 16, 64, 132, 2, 17, 0, 0, 0, 8, 241, 136, 200, 168, 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: