Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 073397490eb8017831d2e94c504673a1d7cc4e7abc3f74ff7af4e3d80159265c

Tx prefix hash: 41b31e39f53819cf3a11eb84025b06aba77dc75ed29a125047ed1c703379d367
Tx public key: 0cc62f2beb9f42b382e23efe646ccdc64344dee57a39b6f0fb7e2eba666914ef
Timestamp: 1775190384 Timestamp [UTC]: 2026-04-03 04:26:24 Age [y:d:h:m:s]: 00:228:11:49:20
Block: 1511695 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168791 RingCT/type: yes/0
Extra: 010cc62f2beb9f42b382e23efe646ccdc64344dee57a39b6f0fb7e2eba666914ef021100000005e3d7dc9f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3b411a3c4664db37e2b7ce23bc3b2d2cc30b55a83e06995c85a41a421646d219 0.000600000000 2001489 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": 1511705, "vin": [ { "gen": { "height": 1511695 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b411a3c4664db37e2b7ce23bc3b2d2cc30b55a83e06995c85a41a421646d219" } } ], "extra": [ 1, 12, 198, 47, 43, 235, 159, 66, 179, 130, 226, 62, 254, 100, 108, 205, 198, 67, 68, 222, 229, 122, 57, 182, 240, 251, 126, 46, 186, 102, 105, 20, 239, 2, 17, 0, 0, 0, 5, 227, 215, 220, 159, 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: