Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d51806793259a29f292a598cb6a5109109d4553345ebc0b528cdfcecdfd3aa2

Tx prefix hash: 29e6e189cf13eb07f57d08832e37e09a1cbf4fa07d70fc6fb923bbec8213c648
Tx public key: ea96ffe1cc0114ac96c903600924b83248b7a2e5b878a6403752fafc0a057bf8
Timestamp: 1783954677 Timestamp [UTC]: 2026-07-13 14:57:57 Age [y:d:h:m:s]: 00:132:03:14:04
Block: 1581426 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 102068 RingCT/type: yes/0
Extra: 01ea96ffe1cc0114ac96c903600924b83248b7a2e5b878a6403752fafc0a057bf8020826fd6f7e0ba891e6

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a93d0cda79d9521eb2aaa74d5a8943e0c6c30e7ae0e293159f2d5d28e31ec766 0.000600000000 2071418 of 15 <c4>

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": 1581436, "vin": [ { "gen": { "height": 1581426 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "a93d0cda79d9521eb2aaa74d5a8943e0c6c30e7ae0e293159f2d5d28e31ec766", "view_tag": "c4" } } } ], "extra": [ 1, 234, 150, 255, 225, 204, 1, 20, 172, 150, 201, 3, 96, 9, 36, 184, 50, 72, 183, 162, 229, 184, 120, 166, 64, 55, 82, 250, 252, 10, 5, 123, 248, 2, 8, 38, 253, 111, 126, 11, 168, 145, 230 ], "rct_signatures": { "type": 0 } }


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