Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79d0a15720a01cad15354e7ea9da059f0b60e945917250032e7eb5f41bcb2bbf

Tx prefix hash: d19783366abeed355f70a1dfb115b8b4a9e1cae8c7ecc6092ad3040298d21be3
Tx public key: b1baeeef3489fa02ba9b1ac98bfaa895d0de618703cc0f24a16951335c6d5618
Timestamp: 1755298290 Timestamp [UTC]: 2025-08-15 22:51:30 Age [y:d:h:m:s]: 01:094:17:06:13
Block: 1347501 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333724 RingCT/type: yes/0
Extra: 01b1baeeef3489fa02ba9b1ac98bfaa895d0de618703cc0f24a16951335c6d56180211000000018368266d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4ef5817ccb2400f343855a3c2f1ab538cd31690dee4d2198a0bea5f7f221cb99 0.000600000000 1835418 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": 1347511, "vin": [ { "gen": { "height": 1347501 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ef5817ccb2400f343855a3c2f1ab538cd31690dee4d2198a0bea5f7f221cb99" } } ], "extra": [ 1, 177, 186, 238, 239, 52, 137, 250, 2, 186, 155, 26, 201, 139, 250, 168, 149, 208, 222, 97, 135, 3, 204, 15, 36, 161, 105, 81, 51, 92, 109, 86, 24, 2, 17, 0, 0, 0, 1, 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: