Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25e1d1cffbe099a9ecc65aabc3ec7324fd3393eb96c8bba8e14d346290da6ef4

Tx prefix hash: 4e4405d334fc22ed91532bc456d0d7c25424b0ba7a73ed36fd0c8b02c2609a45
Tx public key: 17e9bf87ca3d6fa1dbca1e22b48ab7337647f78d7c5b4032772677eb0bad5d07
Timestamp: 1775148308 Timestamp [UTC]: 2026-04-02 16:45:08 Age [y:d:h:m:s]: 00:225:17:19:18
Block: 1511350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166715 RingCT/type: yes/0
Extra: 0117e9bf87ca3d6fa1dbca1e22b48ab7337647f78d7c5b4032772677eb0bad5d07021100000002e3d7dc9f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a0ec291b22af0cbc6e44e0af1bba2a4f75c87b04feab1bd01e8096a80cda5d55 0.000600000000 2001142 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": 1511360, "vin": [ { "gen": { "height": 1511350 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0ec291b22af0cbc6e44e0af1bba2a4f75c87b04feab1bd01e8096a80cda5d55" } } ], "extra": [ 1, 23, 233, 191, 135, 202, 61, 111, 161, 219, 202, 30, 34, 180, 138, 183, 51, 118, 71, 247, 141, 124, 91, 64, 50, 119, 38, 119, 235, 11, 173, 93, 7, 2, 17, 0, 0, 0, 2, 227, 215, 220, 159, 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: