← previous blocknext block →recent activity
Analyzing
Block #91,407,638
15 transactions · 13 stateful · 2026-07-29 17:49:56 UTC
Parallelism
67/100
Blocked
46%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,407,638 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w19w210w312w413w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb852cf41…12b6
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x05940581…ae33
0x34b655…2a6f
6 touches
3 conflicts
0xd4dfefe7…b85f
0x34b655…2a6f
6 touches
3 conflicts
0x5655fc91…96ba
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x94f2c3b4…4ef6
0x34b655…2a6f
4 touches
1 conflict
0x9feb7f16…58ee
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
6 conflicts on slot 0xb852cf419d…4b12b6
Audit this contract →
← previous block·next block →recent activity