Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5cbd3e169545415b471908e0f1b5fc9b4d8ed05ca66753acc718a899d4eb8be0

Tx prefix hash: 64ded785f2f102d55617e4179f625cca4625448f057f54b3abb6765db82a69e4
Tx public key: ef28797565e551f3dfe8b25ee45441741b34e5bfc3b7519f84f2aae038fc358a
Timestamp: 1770704724 Timestamp [UTC]: 2026-02-10 06:25:24 Age [y:d:h:m:s]: 00:283:05:45:59
Block: 1474605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 208068 RingCT/type: yes/0
Extra: 01ef28797565e551f3dfe8b25ee45441741b34e5bfc3b7519f84f2aae038fc358a0208c7acf1ad0d7edc9f

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 67a272558d46fd1a6b30c198c261d1a30b198e72fb9ecc34e6cbeb9967749fad 0.000600000000 1963903 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": 1474615, "vin": [ { "gen": { "height": 1474605 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67a272558d46fd1a6b30c198c261d1a30b198e72fb9ecc34e6cbeb9967749fad" } } ], "extra": [ 1, 239, 40, 121, 117, 101, 229, 81, 243, 223, 232, 178, 94, 228, 84, 65, 116, 27, 52, 229, 191, 195, 183, 81, 159, 132, 242, 170, 224, 56, 252, 53, 138, 2, 8, 199, 172, 241, 173, 13, 126, 220, 159 ], "rct_signatures": { "type": 0 } }


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