Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a333dfe546a752398bf61340af9c612b3f46040d3a38c2d0738e5e8d7e077a3

Tx prefix hash: cd2ed8b092859d0e0555705951fd8e5d5070837a9db5db67bfc1cdf50c88a2b4
Tx public key: 1ccb6e76e579538796e9d5cdd73c43e5bb06bd3a3a187a9ee256b312231c4e61
Timestamp: 1750244396 Timestamp [UTC]: 2025-06-18 10:59:56 Age [y:d:h:m:s]: 01:156:15:22:29
Block: 1307613 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375881 RingCT/type: yes/0
Extra: 011ccb6e76e579538796e9d5cdd73c43e5bb06bd3a3a187a9ee256b312231c4e61021100000005bf51b2a2000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: aef7a4ed1d8a21e04f87021cfdb093d6059b84f325866e253b02f96e6b8e37de 0.000600000000 1795224 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": 1307623, "vin": [ { "gen": { "height": 1307613 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aef7a4ed1d8a21e04f87021cfdb093d6059b84f325866e253b02f96e6b8e37de" } } ], "extra": [ 1, 28, 203, 110, 118, 229, 121, 83, 135, 150, 233, 213, 205, 215, 60, 67, 229, 187, 6, 189, 58, 58, 24, 122, 158, 226, 86, 179, 18, 35, 28, 78, 97, 2, 17, 0, 0, 0, 5, 191, 81, 178, 162, 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: