← previous blocknext block →recent activity
Analyzing
Block #91,798,932
11 transactions · 11 stateful · 2026-07-31 02:39:24 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,798,932 · 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
2w06w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc069c43…5538
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4b2
0x34b655…2a6f
4 touches
1 conflict
0x809c6c4f…c919
0x34b655…2a6f
4 touches
1 conflict
0x86388328…bd17
0x34b655…2a6f
4 touches
1 conflict
0x8b1192df…23f2
0x34b655…2a6f
4 touches
1 conflict
0xb9834665…e363
0x34b655…2a6f
4 touches
1 conflict
0xbed5ddf9…d1d2
0x34b655…2a6f
4 touches
1 conflict
0xe1059021…21ec
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
1 conflict on slot 0xfc069c43f6…135538
Audit this contract →
← previous block·next block →recent activity