Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 535fad78837c5b6a330c4bb631579c71c3fe1fe602258b3ddc53aa30e9067aa6

Tx prefix hash: ca0fae4b17b57ec0f458723d35bcfabd608d7addd2405686fbe4f210355c2d75
Tx public key: 5e2910dadc4cf7478bafb34bc9f7d23aa251d4b2f737058eefff094318fab1ac
Timestamp: 1783203205 Timestamp [UTC]: 2026-07-04 22:13:25 Age [y:d:h:m:s]: 00:134:21:52:46
Block: 1574789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 105088 RingCT/type: yes/0
Extra: 015e2910dadc4cf7478bafb34bc9f7d23aa251d4b2f737058eefff094318fab1ac0208845235ae638b15d1

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 64a5b6e04f74b897d4eb7b17534b5f545b9d03e495c71cac64d258d2082cb773 0.000600000000 2064771 of 15 <d3>

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": 1574799, "vin": [ { "gen": { "height": 1574789 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "64a5b6e04f74b897d4eb7b17534b5f545b9d03e495c71cac64d258d2082cb773", "view_tag": "d3" } } } ], "extra": [ 1, 94, 41, 16, 218, 220, 76, 247, 71, 139, 175, 179, 75, 201, 247, 210, 58, 162, 81, 212, 178, 247, 55, 5, 142, 239, 255, 9, 67, 24, 250, 177, 172, 2, 8, 132, 82, 53, 174, 99, 139, 21, 209 ], "rct_signatures": { "type": 0 } }


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