Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 374697b87ddff6c14e847a96d2113cb137d570dbc61f96a84ee4f54bbf1f6000

Tx prefix hash: a1abd9655f9f9760e63cc8d769c8613c3b7785d216f1f094c27fa2449a036cf5
Tx public key: c65a755ca7071ca0d400c657132e5c1a09ce4016030240d6e3f033c9fa431818
Timestamp: 1748941861 Timestamp [UTC]: 2025-06-03 09:11:01 Age [y:d:h:m:s]: 01:168:03:33:21
Block: 1296960 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384176 RingCT/type: yes/0
Extra: 01c65a755ca7071ca0d400c657132e5c1a09ce4016030240d6e3f033c9fa43181802110000000143846d66000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7222a61490beedd763b2e40c8dab93ac641a1e511bd729508a71fffdce387cb3 0.000600000000 1784477 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": 1296970, "vin": [ { "gen": { "height": 1296960 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7222a61490beedd763b2e40c8dab93ac641a1e511bd729508a71fffdce387cb3" } } ], "extra": [ 1, 198, 90, 117, 92, 167, 7, 28, 160, 212, 0, 198, 87, 19, 46, 92, 26, 9, 206, 64, 22, 3, 2, 64, 214, 227, 240, 51, 201, 250, 67, 24, 24, 2, 17, 0, 0, 0, 1, 67, 132, 109, 102, 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: