Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 287bb1f9146a5ad556ead4e01437aaf2135d2b94bd0836ed2085095ddb2e9ca9

Tx prefix hash: 020d9c9313dbc09cd07968942e0506794a2abb6b1ae255f1fb628bfd09bfa6ad
Tx public key: af50b2b2b00b68854069e725ae1fb31a3f4e43c9cf0ef37134fe1a4eaa94f355
Timestamp: 1787187691 Timestamp [UTC]: 2026-08-20 01:01:31 Age [y:d:h:m:s]: 00:091:04:12:51
Block: 1617150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 64510 RingCT/type: yes/0
Extra: 01af50b2b2b00b68854069e725ae1fb31a3f4e43c9cf0ef37134fe1a4eaa94f35502081c5a919b83a2aeda

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 699aef1b573e2e84d997da427c2807584ef9352ac0cb4737128cdbb0a059abcd 0.000600000000 2107170 of 15 <a3>

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": 1617160, "vin": [ { "gen": { "height": 1617150 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "699aef1b573e2e84d997da427c2807584ef9352ac0cb4737128cdbb0a059abcd", "view_tag": "a3" } } } ], "extra": [ 1, 175, 80, 178, 178, 176, 11, 104, 133, 64, 105, 231, 37, 174, 31, 179, 26, 63, 78, 67, 201, 207, 14, 243, 113, 52, 254, 26, 78, 170, 148, 243, 85, 2, 8, 28, 90, 145, 155, 131, 162, 174, 218 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: