Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edc703a6ccdfbadeb4540ad97da7c9f440562b2a185b808ed105de3242c03d8b

Tx prefix hash: 9441bc323f821f6178a91c9184841ad3ebfec488f520cfef529feb96c534b26d
Tx public key: b86545f3a5f1ac517bfb744656c704a98cdeafb2ec631fd94491651b4189f56e
Timestamp: 1737979104 Timestamp [UTC]: 2025-01-27 11:58:24 Age [y:d:h:m:s]: 01:128:15:32:08
Block: 1206223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345361 RingCT/type: yes/0
Extra: 01b86545f3a5f1ac517bfb744656c704a98cdeafb2ec631fd94491651b4189f56e0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ef789f2b791c60d0e1c1e983fb293fc8ee88bb74d4695482ca89cc728ef0cc60 0.000600000000 1692926 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": 1206233, "vin": [ { "gen": { "height": 1206223 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef789f2b791c60d0e1c1e983fb293fc8ee88bb74d4695482ca89cc728ef0cc60" } } ], "extra": [ 1, 184, 101, 69, 243, 165, 241, 172, 81, 123, 251, 116, 70, 86, 199, 4, 169, 140, 222, 175, 178, 236, 99, 31, 217, 68, 145, 101, 27, 65, 137, 245, 110, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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: