← previous blocknext block →recent activity
Analyzing
Block #91,424,495
40 transactions · 33 stateful · 2026-07-29 19:15:11 UTC
Parallelism
75/100
Blocked
64%
Avg conflicts / tx
1.5
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #91,424,495 · 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
4w05w16w09w212w013w114w216w317w418w419w320w322w423w530w631w732w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…004c
0x80c745…7210
10 touches
10 conflicts
0x1bf8d2af…d140
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…004b
0x80c745…7210
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xbba9dcbb…e4c9
0x34b655…2a6f
8 touches
6 conflicts
0xc0eb79d1…29a4
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 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: 0x80c74517…647210
10 conflicts on slot 0x0000000000…00004c
Audit this contract →
← previous block·next block →recent activity