Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4892af29d239995e09ff3d79df10edfb544a3b07286f13e08a8e0066f4f6a9b5

Tx prefix hash: 0c57bb65a58b25073a2fb2f5151d6e4c7b7a4e70f1495928011ade2e2688684a
Tx public key: eff118a09806fa18902949fea259188131477baac4fca08fca0c506c5af5dad7
Timestamp: 1656612323 Timestamp [UTC]: 2022-06-30 18:05:23 Age [y:d:h:m:s]: 04:145:00:36:28
Block: 533761 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1149733 RingCT/type: yes/0
Extra: 01eff118a09806fa18902949fea259188131477baac4fca08fca0c506c5af5dad702110000000a75e3f0e9000000000000000000

1 output(s) for total of 0.010457512403 xmr

stealth address amount amount idx tag
00: b07683096c1871ee80b1527d01791f1f3c3a5fff6c1d4b5a6ac30ae1a57283b6 0.010457512403 963116 of 0 -

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": 533771, "vin": [ { "gen": { "height": 533761 } } ], "vout": [ { "amount": 10457512403, "target": { "key": "b07683096c1871ee80b1527d01791f1f3c3a5fff6c1d4b5a6ac30ae1a57283b6" } } ], "extra": [ 1, 239, 241, 24, 160, 152, 6, 250, 24, 144, 41, 73, 254, 162, 89, 24, 129, 49, 71, 123, 170, 196, 252, 160, 143, 202, 12, 80, 108, 90, 245, 218, 215, 2, 17, 0, 0, 0, 10, 117, 227, 240, 233, 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: