← previous blocknext block →recent activity

Analyzing

Block #75,552,180

11 transactions · 11 stateful · 2026-05-19 05:44:33 UTC

Parallelism

64/100

Blocked

36%

Avg conflicts / tx

0.45

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #75,552,180  ·  11 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x5f77d607…2c84

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x8777ff60…fc77

0x065c9d…c394

3 touches
1 conflict

0x65f5a5c4…43ca

0xd32edf…ff58

3 touches
1 conflict

0x443a3e47…f4a4

0x065c9d…c394

2 touches
0 conflicts

0xe5ad0a15…cfad

0x065c9d…c394

2 touches
0 conflicts

0xf5446f2b…9292

0x065c9d…c394

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

2 touches
0 conflicts

What's blocking what?

Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.

The bottleneck

Throughput-killer: Kuru Exchange: Market-MON/USDC

3 conflicts on slot 0x5f77d60791…b12c84

← previous block·next block →recent activity