Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b355586e2bbda4b5f02f416df3fde7ad2e42131db413b3168aa51dff404c7d91

Tx prefix hash: df054e48f90773c4f9e5924234ea0df7dac43af775a12b137da55d62980a0dd6
Tx public key: 6c026b1ab1814dfe94c25bb9479f7790f6c5f91d19d2149c59d5947f3498b264
Timestamp: 1782984147 Timestamp [UTC]: 2026-07-02 09:22:27 Age [y:d:h:m:s]: 00:140:22:13:26
Block: 1572926 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 109585 RingCT/type: yes/0
Extra: 016c026b1ab1814dfe94c25bb9479f7790f6c5f91d19d2149c59d5947f3498b264

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c2470293487804a540f2f761642499eb3c61ebaea329723cd5aca8c86d107245 0.000600000000 2062906 of 15 <b0>

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": 1572936, "vin": [ { "gen": { "height": 1572926 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "c2470293487804a540f2f761642499eb3c61ebaea329723cd5aca8c86d107245", "view_tag": "b0" } } } ], "extra": [ 1, 108, 2, 107, 26, 177, 129, 77, 254, 148, 194, 91, 185, 71, 159, 119, 144, 246, 197, 249, 29, 25, 210, 20, 156, 89, 213, 148, 127, 52, 152, 178, 100 ], "rct_signatures": { "type": 0 } }


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