Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1aea3efd99887110bea036d5187ebbd07d86fca6447971a48f9bde81b40bbd56

Tx prefix hash: 1b856509da4c6e23f527bfb8aa2316ec724bcee9795ced392cb9297a0f73bc2a
Tx public key: 1f3be85d6582f0f353e7e8d86fa77387729cac9212065b24f4d8f2d82fc1b9b2
Timestamp: 1743111534 Timestamp [UTC]: 2025-03-27 21:38:54 Age [y:d:h:m:s]: 01:053:18:55:42
Block: 1248667 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290450 RingCT/type: yes/0
Extra: 011f3be85d6582f0f353e7e8d86fa77387729cac9212065b24f4d8f2d82fc1b9b2021100000001d8e7d241000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a1930b9a927a460ffb090edeb8fa9d904c1cf38a58ff89c63cbd42db7bdacec9 0.000600000000 1735700 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": 1248677, "vin": [ { "gen": { "height": 1248667 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1930b9a927a460ffb090edeb8fa9d904c1cf38a58ff89c63cbd42db7bdacec9" } } ], "extra": [ 1, 31, 59, 232, 93, 101, 130, 240, 243, 83, 231, 232, 216, 111, 167, 115, 135, 114, 156, 172, 146, 18, 6, 91, 36, 244, 216, 242, 216, 47, 193, 185, 178, 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: