← previous blocknext block →recent activity
Analyzing
Block #91,408,291
20 transactions · 18 stateful · 2026-07-29 17:53:14 UTC
Parallelism
70/100
Blocked
39%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,408,291 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w310w415w518w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x010b6bfe…4581
0x34b655…2a6f
6 touches
3 conflicts
0xd9461b7e…31bc
0x34b655…2a6f
6 touches
3 conflicts
0xc53799eb…d928
0x34b655…2a6f
4 touches
1 conflict
0xc799e56d…45aa
0x34b655…2a6f
4 touches
1 conflict
0x2e7a0c1d…caaf
0x34b655…2a6f
4 touches
1 conflict
0x2c66ecd1…f41d
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity