Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1e61a7eea43d6bb5a93603a16e9e076cd4d4e50879780ba46aead6f879c5b89

Tx prefix hash: ede2fb871b045afeb48f41d0d19987bd888f269a7884e9ba64f5738df1293174
Tx public key: cc257feee59f6f9ebf42376aef486719684ea21f63fc175a367bcf30872bab5f
Timestamp: 1772245771 Timestamp [UTC]: 2026-02-28 02:29:31 Age [y:d:h:m:s]: 00:263:21:18:31
Block: 1487329 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194154 RingCT/type: yes/0
Extra: 01cc257feee59f6f9ebf42376aef486719684ea21f63fc175a367bcf30872bab5f021100000007e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 77bb9e134e49e3c3998b6289ff9e8ddd6b4d8542fe3e7a25c7c9d89a2e4ff7df 0.000600000000 1976797 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": 1487339, "vin": [ { "gen": { "height": 1487329 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77bb9e134e49e3c3998b6289ff9e8ddd6b4d8542fe3e7a25c7c9d89a2e4ff7df" } } ], "extra": [ 1, 204, 37, 127, 238, 229, 159, 111, 158, 191, 66, 55, 106, 239, 72, 103, 25, 104, 78, 162, 31, 99, 252, 23, 90, 54, 123, 207, 48, 135, 43, 171, 95, 2, 17, 0, 0, 0, 7, 228, 245, 25, 63, 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: