Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae2a20076e06bc3958802955cc6a04e467d7a980bc669a99deead94cff4ce3ee

Tx prefix hash: e63f49f9f98c7a1764008cafba41ac15b877f56fa6a1f5d76c3320c22295e151
Tx public key: 5d8da3664394b11ea4eb29bfa66de582e30a821684a1b50731f9934a8ae7808c
Timestamp: 1754236734 Timestamp [UTC]: 2025-08-03 15:58:54 Age [y:d:h:m:s]: 01:107:14:32:57
Block: 1339501 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342195 RingCT/type: yes/0
Extra: 015d8da3664394b11ea4eb29bfa66de582e30a821684a1b50731f9934a8ae7808c021100000001d8e7d241000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e77d411528943b64e1425a9bdb339b988f55203b061ed1b590045166915e6d75 0.000600000000 1827316 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": 1339511, "vin": [ { "gen": { "height": 1339501 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e77d411528943b64e1425a9bdb339b988f55203b061ed1b590045166915e6d75" } } ], "extra": [ 1, 93, 141, 163, 102, 67, 148, 177, 30, 164, 235, 41, 191, 166, 109, 229, 130, 227, 10, 130, 22, 132, 161, 181, 7, 49, 249, 147, 74, 138, 231, 128, 140, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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: