Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b478b619730834cede72f97cfc81a58b36afbd3f7cdb236689e0b3c5c1789caa

Tx prefix hash: cf92fd5a778a39d132484e8d2568e249ef7fc805003e3b38ae07fd9f737db234
Tx public key: 61e525db587445ef82f92c021c7dd04da5e827cc1ba9976b3f8174fa42645d8e
Timestamp: 1784340281 Timestamp [UTC]: 2026-07-18 02:04:41 Age [y:d:h:m:s]: 00:125:16:23:01
Block: 1584169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 98692 RingCT/type: yes/0
Extra: 0161e525db587445ef82f92c021c7dd04da5e827cc1ba9976b3f8174fa42645d8e02087a213853be4d0716

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8f4c7fa3d034e1dd895b74c5685bee3afc37b01ec7cb6c58f17ed42e059dbada 0.000600000000 2074163 of 15 <10>

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": 1584179, "vin": [ { "gen": { "height": 1584169 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "8f4c7fa3d034e1dd895b74c5685bee3afc37b01ec7cb6c58f17ed42e059dbada", "view_tag": "10" } } } ], "extra": [ 1, 97, 229, 37, 219, 88, 116, 69, 239, 130, 249, 44, 2, 28, 125, 208, 77, 165, 232, 39, 204, 27, 169, 151, 107, 63, 129, 116, 250, 66, 100, 93, 142, 2, 8, 122, 33, 56, 83, 190, 77, 7, 22 ], "rct_signatures": { "type": 0 } }


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