Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6e11997e7382a0c1fcf7922dcbb2f467adfae8bcaf71f95946ea945703d9a5e

Tx prefix hash: d23b9f53a2376e12c5f5af9091a83687183cfb21fc6303a434897920c10df038
Tx public key: 420ad352026b63112b72b9ff26bad84d4efb07190b88b2f93e6322a3848c62f8
Timestamp: 1772666392 Timestamp [UTC]: 2026-03-04 23:19:52 Age [y:d:h:m:s]: 00:260:08:26:05
Block: 1490823 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191696 RingCT/type: yes/0
Extra: 01420ad352026b63112b72b9ff26bad84d4efb07190b88b2f93e6322a3848c62f8021100000001da554848000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 416422b72f181a8dfa4de96222fd3df9cd18f2757a8322858e70aff4e4f9a12d 0.000600000000 1980333 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": 1490833, "vin": [ { "gen": { "height": 1490823 } } ], "vout": [ { "amount": 600000000, "target": { "key": "416422b72f181a8dfa4de96222fd3df9cd18f2757a8322858e70aff4e4f9a12d" } } ], "extra": [ 1, 66, 10, 211, 82, 2, 107, 99, 17, 43, 114, 185, 255, 38, 186, 216, 77, 78, 251, 7, 25, 11, 136, 178, 249, 62, 99, 34, 163, 132, 140, 98, 248, 2, 17, 0, 0, 0, 1, 218, 85, 72, 72, 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: