← previous blocknext block →recent activity
Analyzing
Block #93,346,741
40 transactions · 34 stateful · 2026-08-05 12:27:03 UTC
Parallelism
75/100
Blocked
62%
Avg conflicts / tx
1.77
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #93,346,741 · 40 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w49w525w627w728w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
16 touches
28 conflicts
0xf219f7cf…7379
0xa6afd3…d132
14 touches
21 conflicts
0xc782ec05…5bb2
0xa6afd3…d132
14 touches
21 conflicts
0x889d5e90…929a
0x2a68ba…90c5
12 touches
15 conflicts
0xdb067026…9eb8
0x2b46c0…1669
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x5778d110…d2e6
0xc8689a…ee79
10 touches
10 conflicts
0x40970e69…da50
0x2b46c0…1669
10 touches
10 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-WETH/USDC
28 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity