← previous blocknext block →recent activity
Analyzing
Block #91,905,970
6 transactions · 6 stateful · 2026-07-31 11:37:58 UTC
Parallelism
67/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,905,970 · 6 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbbeac3b7…c14b
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x6518075e…2b17
0x2a68ba…90c5
2 touches
0 conflicts
0x001d91db…8b3c
0x34b655…2a6f
2 touches
0 conflicts
0x1bb56de3…732e
0x34b655…2a6f
2 touches
0 conflicts
0x342222e8…2ec4
0x34b655…2a6f
2 touches
0 conflicts
0x3dae5ee1…721b
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 0xbbeac3b703…d0c14b
Audit this contract →
← previous block·next block →recent activity