Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad5fc8232709f3697faed4267ace0d7a596bf4a0c22424d98d7be536ecfd71a4

Tx prefix hash: 302922efc897fe1d8fe153b074655db499df652a934dd352410031218d3bb4ee
Tx public key: c6f029fc7a947d5ecae40879ae66cda182f7e582866406caeffb0554ff3764cb
Timestamp: 1717394392 Timestamp [UTC]: 2024-06-03 05:59:52 Age [y:d:h:m:s]: 02:169:00:30:37
Block: 1035973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 645722 RingCT/type: yes/0
Extra: 01c6f029fc7a947d5ecae40879ae66cda182f7e582866406caeffb0554ff3764cb02110000000759dad3f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 80cbc6a0e5bb6a1f16120ca0635597189464c946376c12057d667031cc62e874 0.000600000000 1504498 of 15 -

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": 1035983, "vin": [ { "gen": { "height": 1035973 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80cbc6a0e5bb6a1f16120ca0635597189464c946376c12057d667031cc62e874" } } ], "extra": [ 1, 198, 240, 41, 252, 122, 148, 125, 94, 202, 228, 8, 121, 174, 102, 205, 161, 130, 247, 229, 130, 134, 100, 6, 202, 239, 251, 5, 84, 255, 55, 100, 203, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


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