← previous blocknext block →recent activity
Analyzing
Block #91,836,623
13 transactions · 12 stateful · 2026-07-31 05:49:01 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,836,623 · 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
4w05w06w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe21234e7…bded
0x34b655…2a6f
4 touches
1 conflict
0x25cd5b70…007a
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x7aae2cc9…d355
0x34b655…2a6f
4 touches
1 conflict
0x0a255626…48e1
0x34b655…2a6f
4 touches
1 conflict
0xc56b390b…e0ce
0x34b655…2a6f
4 touches
1 conflict
0xcf5df329…a619
0x34b655…2a6f
4 touches
1 conflict
0xb7fefa89…54dc
0x754704…b603
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 0xe21234e760…98bded
Audit this contract →
← previous block·next block →recent activity