← previous blocknext block →recent activity
Analyzing
Block #91,398,765
10 transactions · 8 stateful · 2026-07-29 17:05:03 UTC
Parallelism
80/100
Blocked
25%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,398,765 · 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
1w04w06w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c51d9aa…af39
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x9dd0a735…4d04
0x34b655…2a6f
4 touches
1 conflict
0x18e900fa…07f4
0x34b655…2a6f
2 touches
0 conflicts
0x2623e991…c9b4
0x34b655…2a6f
2 touches
0 conflicts
0x2b75a9fa…e17b
0x34b655…2a6f
2 touches
0 conflicts
0x2c66ecd1…f41d
0x34b655…2a6f
2 touches
0 conflicts
0x4473e0b1…af47
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 0x7c51d9aa1a…7faf39
Audit this contract →
← previous block·next block →recent activity