← previous blocknext block →recent activity
Analyzing
Block #91,407,243
10 transactions · 9 stateful · 2026-07-29 17:47:53 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,407,243 · 10 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
2w04w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb39cb1d8…effa
0x34b655…2a6f
4 touches
1 conflict
0xb5924647…4cf1
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x76e85a07…5ff1
0x34b655…2a6f
4 touches
1 conflict
0x0b7bd288…2064
0x34b655…2a6f
2 touches
0 conflicts
0x149ea1fb…e34a
0x34b655…2a6f
2 touches
0 conflicts
0x411b1c71…763d
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 0xb39cb1d8c6…28effa
Audit this contract →
← previous block·next block →recent activity