Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0dfcc2bb355771e5638977fed224966de36be33ca3db64c695d82dde3a1e5a5c

Tx prefix hash: 37f01bc205497a763966eff5bfee2bc6d51b8c24a05958aa9eceb04c8f756631
Tx public key: 1ecac82423d0bc7b2d39e5a3b4bc8269d45eba2e2c1981a0a8e719a9bc814a58
Timestamp: 1742088991 Timestamp [UTC]: 2025-03-16 01:36:31 Age [y:d:h:m:s]: 01:249:12:23:41
Block: 1240228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 442510 RingCT/type: yes/0
Extra: 011ecac82423d0bc7b2d39e5a3b4bc8269d45eba2e2c1981a0a8e719a9bc814a580211000000011f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b60cd5129c230f24badd89b9ea9ee45ee28a019a209127e345625791d1ccf7b2 0.000600000000 1727193 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": 1240238, "vin": [ { "gen": { "height": 1240228 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b60cd5129c230f24badd89b9ea9ee45ee28a019a209127e345625791d1ccf7b2" } } ], "extra": [ 1, 30, 202, 200, 36, 35, 208, 188, 123, 45, 57, 229, 163, 180, 188, 130, 105, 212, 94, 186, 46, 44, 25, 129, 160, 168, 231, 25, 169, 188, 129, 74, 88, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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: