Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 160babcb34665c20f43bc985cfebee404018bf125efbcd0451a587641517a082

Tx prefix hash: ddca1762410795b662aa05d8cc9ef1b3730382f9a8b5bb8f6ef2fbf602b9f14e
Tx public key: 4fc7811ab0a38b5abf14e96bebbe35bd59d2ed5e7887cb013e028038fc009d91
Timestamp: 1783112287 Timestamp [UTC]: 2026-07-03 20:58:07 Age [y:d:h:m:s]: 00:140:23:05:04
Block: 1574022 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 109472 RingCT/type: yes/0
Extra: 014fc7811ab0a38b5abf14e96bebbe35bd59d2ed5e7887cb013e028038fc009d910208bae65418ec39a8cf

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9c59c2d693695803d173831b368981a504074fb81edc6a99a130a899f7541bff 0.000600000000 2064002 of 15 <b9>

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": 1574032, "vin": [ { "gen": { "height": 1574022 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "9c59c2d693695803d173831b368981a504074fb81edc6a99a130a899f7541bff", "view_tag": "b9" } } } ], "extra": [ 1, 79, 199, 129, 26, 176, 163, 139, 90, 191, 20, 233, 107, 235, 190, 53, 189, 89, 210, 237, 94, 120, 135, 203, 1, 62, 2, 128, 56, 252, 0, 157, 145, 2, 8, 186, 230, 84, 24, 236, 57, 168, 207 ], "rct_signatures": { "type": 0 } }


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