Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 378dd949f7d486c44dbf59c22754c4c86cd4b7b60eb23ed1df8c84d8a66bf270

Tx prefix hash: a7e23ec0e80760d3d3f6d44d05ce952c4fec568bf8e8624b83accd48208dd31f
Tx public key: 32070a99fba1a5a0eb76d25a856bd5e8a02fab6987eba3c35687c2882859cd72
Timestamp: 1784001948 Timestamp [UTC]: 2026-07-14 04:05:48 Age [y:d:h:m:s]: 00:128:06:33:59
Block: 1581845 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 99980 RingCT/type: yes/0
Extra: 0132070a99fba1a5a0eb76d25a856bd5e8a02fab6987eba3c35687c2882859cd720208538ae6af54922fc4

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 16e96f9074d7ce7df4b5816d61b697cb0b83d1aee62d01b72333936f88dab030 0.000600000000 2071837 of 15 <28>

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": 1581855, "vin": [ { "gen": { "height": 1581845 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "16e96f9074d7ce7df4b5816d61b697cb0b83d1aee62d01b72333936f88dab030", "view_tag": "28" } } } ], "extra": [ 1, 50, 7, 10, 153, 251, 161, 165, 160, 235, 118, 210, 90, 133, 107, 213, 232, 160, 47, 171, 105, 135, 235, 163, 195, 86, 135, 194, 136, 40, 89, 205, 114, 2, 8, 83, 138, 230, 175, 84, 146, 47, 196 ], "rct_signatures": { "type": 0 } }


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