Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64740b59057079ed3fe8ac73e2b43d3464ec619bb2463a1a8a0c7517f87ad3ff

Tx prefix hash: a396d2454b72e22a90fc797c62ce237bdff35f87bc8411774a97953d0a3a68cf
Tx public key: d0f60ab2ac45bf35ab2864c78e1065194dbc14e730144f8dfd34a054574836c3
Timestamp: 1748029085 Timestamp [UTC]: 2025-05-23 19:38:05 Age [y:d:h:m:s]: 01:178:20:12:34
Block: 1289392 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391830 RingCT/type: yes/0
Extra: 01d0f60ab2ac45bf35ab2864c78e1065194dbc14e730144f8dfd34a054574836c302110000000a9f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7816c887fd7bf300637b80aae2f93f090f5c942df210405d1ec827934dc468f5 0.000600000000 1776861 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": 1289402, "vin": [ { "gen": { "height": 1289392 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7816c887fd7bf300637b80aae2f93f090f5c942df210405d1ec827934dc468f5" } } ], "extra": [ 1, 208, 246, 10, 178, 172, 69, 191, 53, 171, 40, 100, 199, 142, 16, 101, 25, 77, 188, 20, 231, 48, 20, 79, 141, 253, 52, 160, 84, 87, 72, 54, 195, 2, 17, 0, 0, 0, 10, 159, 159, 230, 140, 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: