← previous blocknext block →recent activity
Analyzing
Block #91,386,700
11 transactions · 11 stateful · 2026-07-29 16:04:22 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,386,700 · 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
1w03w15w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda27c764…7fab
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x1ed49f47…b6e4
0x34b655…2a6f
4 touches
1 conflict
0x307498ba…0b4d
0x34b655…2a6f
4 touches
1 conflict
0x44b918e8…94d7
0x34b655…2a6f
4 touches
1 conflict
0x4c20364f…d89a
0x34b655…2a6f
4 touches
1 conflict
0x6507044e…bcd6
0x34b655…2a6f
4 touches
1 conflict
0x6784a12f…fca5
0x34b655…2a6f
4 touches
1 conflict
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: Perpl
3 conflicts on slot 0xda27c76455…2e7fab
Audit this contract →
← previous block·next block →recent activity