Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52396541ca5eb0d89b635c1d51bf7490ddbd8e5cd51be4d4e3f6b7fc3d9e3baf

Tx prefix hash: 7278d192a05ca4c71e3ed46b3b77dc24ec8532993f6ffdd9e22c4db658e2bd5e
Tx public key: 16e0173029b2e42acd6b26572189f84001fcdb6a8d4155721cd051a9eb5fff63
Timestamp: 1774343547 Timestamp [UTC]: 2026-03-24 09:12:27 Age [y:d:h:m:s]: 00:237:12:46:03
Block: 1504684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175258 RingCT/type: yes/0
Extra: 0116e0173029b2e42acd6b26572189f84001fcdb6a8d4155721cd051a9eb5fff63021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a20e8e812875120d3aa671570d6adb0e07ea151f9e75bff22a49e460eac54122 0.000600000000 1994410 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": 1504694, "vin": [ { "gen": { "height": 1504684 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a20e8e812875120d3aa671570d6adb0e07ea151f9e75bff22a49e460eac54122" } } ], "extra": [ 1, 22, 224, 23, 48, 41, 178, 228, 42, 205, 107, 38, 87, 33, 137, 248, 64, 1, 252, 219, 106, 141, 65, 85, 114, 28, 208, 81, 169, 235, 95, 255, 99, 2, 17, 0, 0, 0, 3, 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: