← previous blocknext block →recent activity
Analyzing
Block #91,444,536
9 transactions · 9 stateful · 2026-07-29 20:56:34 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,444,536 · 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
2w03w14w26w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8f203394…f2db
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x0b6605df…08f8
0x34b655…2a6f
2 touches
0 conflicts
0x2840c278…bbc7
0x34b655…2a6f
2 touches
0 conflicts
0x28fd1e15…9a1a
0x34b655…2a6f
2 touches
0 conflicts
0x2fa2d1bd…0221
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