Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08c040b7b69c3ad4117ee2435be9d8f251f26e90633c2528c397ecb91d7ef9db

Tx prefix hash: b258f2c009d70a2832b32c54b67365d49ab55f87b0cebe7f3e73b15662eef281
Tx public key: cdffdb0a4b9550f82140f8eeed02da21661a8f2e46b75e5e40656eb40827911a
Timestamp: 1743439144 Timestamp [UTC]: 2025-03-31 16:39:04 Age [y:d:h:m:s]: 01:044:18:06:45
Block: 1251378 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282941 RingCT/type: yes/0
Extra: 01cdffdb0a4b9550f82140f8eeed02da21661a8f2e46b75e5e40656eb40827911a021100000007703241eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6492ef66aad23b94c2d35d84e4ebbf7f7fb23c767c132c3ceff3597d053e27a3 0.000600000000 1738441 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": 1251388, "vin": [ { "gen": { "height": 1251378 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6492ef66aad23b94c2d35d84e4ebbf7f7fb23c767c132c3ceff3597d053e27a3" } } ], "extra": [ 1, 205, 255, 219, 10, 75, 149, 80, 248, 33, 64, 248, 238, 237, 2, 218, 33, 102, 26, 143, 46, 70, 183, 94, 94, 64, 101, 110, 180, 8, 39, 145, 26, 2, 17, 0, 0, 0, 7, 112, 50, 65, 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: