← previous blocknext block →recent activity
Analyzing
Block #91,270,568
9 transactions · 9 stateful · 2026-07-29 06:19:52 UTC
Parallelism
78/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,270,568 · 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x54f38877…65d4
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0ab54c30…b88e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x5576b03c…0ece
0x34b655…2a6f
2 touches
0 conflicts
0x57b3b97e…7ca7
0x34b655…2a6f
2 touches
0 conflicts
0x7462b8f2…6312
0x34b655…2a6f
2 touches
0 conflicts
0x8ec95f2b…f4d7
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 0x54f3887796…5165d4
Audit this contract →
← previous block·next block →recent activity