Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c3baf6ce4b9d71a811e73b5fba0cd52b237dc0cdbe1ac8c27a96e4243577691

Tx prefix hash: 2f8cf07eccc4c43e688ab2e73217b083fe312423694e24a36281ec4d3cc3cb4c
Tx public key: e100f88b4cf37aa14f6eb3494669bcd94ff81036959c708a4ac4ff5128d49b05
Timestamp: 1750527456 Timestamp [UTC]: 2025-06-21 17:37:36 Age [y:d:h:m:s]: 00:325:16:26:51
Block: 1309900 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222870 RingCT/type: yes/0
Extra: 01e100f88b4cf37aa14f6eb3494669bcd94ff81036959c708a4ac4ff5128d49b050211000000028368266d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 14cc18b8822fa4cc9f68a72b1a5cb6c08244b53adfd635504584ac2824f9ed23 0.000600000000 1797517 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": 1309910, "vin": [ { "gen": { "height": 1309900 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14cc18b8822fa4cc9f68a72b1a5cb6c08244b53adfd635504584ac2824f9ed23" } } ], "extra": [ 1, 225, 0, 248, 139, 76, 243, 122, 161, 79, 110, 179, 73, 70, 105, 188, 217, 79, 248, 16, 54, 149, 156, 112, 138, 74, 196, 255, 81, 40, 212, 155, 5, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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: