← previous blocknext block →recent activity
Analyzing
Block #91,140,185
13 transactions · 12 stateful · 2026-07-28 19:23:11 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,140,185 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0fe1e6e0…f553
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x71bbf601…5874
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x975922f7…be0a
0x34b655…2a6f
2 touches
0 conflicts
0xbc96083d…124d
0x34b655…2a6f
2 touches
0 conflicts
0xd2b44b36…b48d
0x34b655…2a6f
2 touches
0 conflicts
0xddfe6e94…d48b
0x34b655…2a6f
2 touches
0 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: Perpl
1 conflict on slot 0x0fe1e6e0ec…9df553
Audit this contract →
← previous block·next block →recent activity