← previous blocknext block →recent activity
Analyzing
Block #91,139,766
11 transactions · 9 stateful · 2026-07-28 19:21:04 UTC
Parallelism
82/100
Blocked
44%
Avg conflicts / tx
0.36
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,139,766 · 11 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
1w02w13w04w16w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbc66586e…20fe
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xebac0f82…a49c
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x0ca3397e…3644
0x34b655…2a6f
4 touches
1 conflict
0x526f5493…36aa
0x34b655…2a6f
4 touches
1 conflict
0x915c095e…c1e5
0x2b46c0…1669
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 0xbc66586e8f…a220fe
Audit this contract →
← previous block·next block →recent activity