Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5ee3a43eb0722e4b6cb98f2c25174bc568692eaa324a2ae56977ff5bacf12da

Tx prefix hash: 8a5a73d58e3cd731d7cf4d8f2216894480685c58942d04516737924bc6b591e2
Tx public key: c801154bcd6f2dad50bdab23d9371b303353052f17e979655503d4fd1a8fd1b7
Timestamp: 1750666042 Timestamp [UTC]: 2025-06-23 08:07:22 Age [y:d:h:m:s]: 01:149:12:02:19
Block: 1311006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371118 RingCT/type: yes/0
Extra: 01c801154bcd6f2dad50bdab23d9371b303353052f17e979655503d4fd1a8fd1b7021100000004bf51b2a2000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 16f831d5789f21951c242d63f03109dbb5d10a4d4f83fcdcbb3ed4c232ed1241 0.000600000000 1798631 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": 1311016, "vin": [ { "gen": { "height": 1311006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16f831d5789f21951c242d63f03109dbb5d10a4d4f83fcdcbb3ed4c232ed1241" } } ], "extra": [ 1, 200, 1, 21, 75, 205, 111, 45, 173, 80, 189, 171, 35, 217, 55, 27, 48, 51, 83, 5, 47, 23, 233, 121, 101, 85, 3, 212, 253, 26, 143, 209, 183, 2, 17, 0, 0, 0, 4, 191, 81, 178, 162, 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: