Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4bed9d2e3d9f3f3d3c8d6ece90b8aa82bc735ca5b41b4fd61f2ffacbbdce1d0

Tx prefix hash: 7b45c13ed3abd4ef2e1d8880d1dca2aabb8f6ba4afff512ca0e19088e473a899
Tx public key: 6eebed0628adb2154dbf948616dace2a6f7d882a6ba047a4939c2b5071e5d08d
Timestamp: 1771442947 Timestamp [UTC]: 2026-02-18 19:29:07 Age [y:d:h:m:s]: 00:272:06:06:20
Block: 1480696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200093 RingCT/type: yes/0
Extra: 016eebed0628adb2154dbf948616dace2a6f7d882a6ba047a4939c2b5071e5d08d021100000007e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5a66959837d5cc202a3fce11bf75d3a266b54821afc9ab289661bc652b1a2279 0.000600000000 1970066 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": 1480706, "vin": [ { "gen": { "height": 1480696 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a66959837d5cc202a3fce11bf75d3a266b54821afc9ab289661bc652b1a2279" } } ], "extra": [ 1, 110, 235, 237, 6, 40, 173, 178, 21, 77, 191, 148, 134, 22, 218, 206, 42, 111, 125, 136, 42, 107, 160, 71, 164, 147, 156, 43, 80, 113, 229, 208, 141, 2, 17, 0, 0, 0, 7, 228, 245, 25, 63, 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: