← previous blocknext block →recent activity
Analyzing
Block #91,011,737
11 transactions · 11 stateful · 2026-07-28 08:36:51 UTC
Parallelism
55/100
Blocked
36%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,011,737 · 11 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
3w05w18w29w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x36a76bd2…1fb0
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x4c619b7d…f4fa
0x34b655…2a6f
4 touches
1 conflict
0x72470f81…c402
0x34b655…2a6f
4 touches
1 conflict
0x7fd12e7b…0a8b
0x34b655…2a6f
4 touches
1 conflict
0xae897e60…a112
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 0x36a76bd264…b01fb0
Audit this contract →
← previous block·next block →recent activity