← previous blocknext block →recent activity
Analyzing
Block #91,289,564
9 transactions · 9 stateful · 2026-07-29 07:55:30 UTC
Parallelism
67/100
Blocked
22%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,289,564 · 9 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x921a58d1…db22
0x34b655…2a6f
4 touches
1 conflict
0x2c4e81fb…c4c8
0x34b655…2a6f
4 touches
1 conflict
0xcc351d6d…256b
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xefcdf197…96a2
0x34b655…2a6f
4 touches
1 conflict
0x317ef0da…202e
0x34b655…2a6f
2 touches
0 conflicts
0x40c5d5cc…d164
0x34b655…2a6f
2 touches
0 conflicts
0x5a492cd4…8b7b
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 0x921a58d196…62db22
Audit this contract →
← previous block·next block →recent activity