← previous blocknext block →recent activity
Analyzing
Block #91,557,849
9 transactions · 8 stateful · 2026-07-30 06:26:40 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,557,849 · 9 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
2w03w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8f203394…f2db
0x34b655…2a6f
4 touches
1 conflict
0x8f203394…f2dc
0x34b655…2a6f
4 touches
1 conflict
0x5a8d5be5…d9a4
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x0d05e294…dfe5
0x34b655…2a6f
2 touches
0 conflicts
0x18e900fa…07f4
0x34b655…2a6f
2 touches
0 conflicts
0x1dd79365…4bab
0x34b655…2a6f
2 touches
0 conflicts
0x3537b0c8…c959
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 0x8f2033941d…ebf2db
Audit this contract →
← previous block·next block →recent activity