Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64f758598304178e8a8bc30bc69b5adec767a7f0c2c91fd1ca9bd9f63a996b50

Tx prefix hash: 7766869175f65460aed0e5b2e5c044c63ad426d74ed1ea3542df3b78fc704fec
Tx public key: b22796a86bc01604870c4b7f06f6ff62511a7f3a0e85d614619e47634ef2a97c
Timestamp: 1784346138 Timestamp [UTC]: 2026-07-18 03:42:18 Age [y:d:h:m:s]: 00:124:21:41:05
Block: 1584220 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 98076 RingCT/type: yes/0
Extra: 01b22796a86bc01604870c4b7f06f6ff62511a7f3a0e85d614619e47634ef2a97c020822ca01c44a6fb82f

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3749980c2641c38c511a773f614964d438fbc354d9d96826b8b2a4e876a4e1e5 0.000600000000 2074214 of 15 <ec>

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": 1584230, "vin": [ { "gen": { "height": 1584220 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "3749980c2641c38c511a773f614964d438fbc354d9d96826b8b2a4e876a4e1e5", "view_tag": "ec" } } } ], "extra": [ 1, 178, 39, 150, 168, 107, 192, 22, 4, 135, 12, 75, 127, 6, 246, 255, 98, 81, 26, 127, 58, 14, 133, 214, 20, 97, 158, 71, 99, 78, 242, 169, 124, 2, 8, 34, 202, 1, 196, 74, 111, 184, 47 ], "rct_signatures": { "type": 0 } }


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