Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: adcc47d5a2e4ad069de3661ccb393d725ec2754574649b8fc9e547bdffdec08f

Tx prefix hash: 32e2b2bcfded07081f40b593fa906c9ed508cec774401c63e56a9130cbb3a309
Tx public key: b0fbfd5543371d9ce81e959d56515639de0c20cb81480cfda6a930944e2c42d6
Timestamp: 1749860893 Timestamp [UTC]: 2025-06-14 00:28:13 Age [y:d:h:m:s]: 01:161:12:13:10
Block: 1304474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379020 RingCT/type: yes/0
Extra: 01b0fbfd5543371d9ce81e959d56515639de0c20cb81480cfda6a930944e2c42d60211000000028368266d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 102c4de36dbb436b50fecf55f1c1a5e9e48519b1259b3a6441dfdc35933b9ca4 0.000600000000 1792063 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": 1304484, "vin": [ { "gen": { "height": 1304474 } } ], "vout": [ { "amount": 600000000, "target": { "key": "102c4de36dbb436b50fecf55f1c1a5e9e48519b1259b3a6441dfdc35933b9ca4" } } ], "extra": [ 1, 176, 251, 253, 85, 67, 55, 29, 156, 232, 30, 149, 157, 86, 81, 86, 57, 222, 12, 32, 203, 129, 72, 12, 253, 166, 169, 48, 148, 78, 44, 66, 214, 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: