Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 443ef140d4def3ccf0de688f9bef42ef28acee289bb7deef781e95decf3a1518

Tx prefix hash: 47812b066d31cf7c72351dddbda246d7e97f2b90c667058d5e0d3975f7675155
Tx public key: 6cb2af03bc3057d9534b934048ff84182896553595d28f79dd7d88a1b322c858
Timestamp: 1742301014 Timestamp [UTC]: 2025-03-18 12:30:14 Age [y:d:h:m:s]: 01:241:09:27:39
Block: 1241981 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 436448 RingCT/type: yes/0
Extra: 016cb2af03bc3057d9534b934048ff84182896553595d28f79dd7d88a1b322c85802110000000d1f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c96a647630d99c2b5c03e1cb5ad412680efa9eea773b74f82bab78f673dc07bb 0.000600000000 1728954 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": 1241991, "vin": [ { "gen": { "height": 1241981 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c96a647630d99c2b5c03e1cb5ad412680efa9eea773b74f82bab78f673dc07bb" } } ], "extra": [ 1, 108, 178, 175, 3, 188, 48, 87, 217, 83, 75, 147, 64, 72, 255, 132, 24, 40, 150, 85, 53, 149, 210, 143, 121, 221, 125, 136, 161, 179, 34, 200, 88, 2, 17, 0, 0, 0, 13, 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: