← previous blocknext block →recent activity
Analyzing
Block #91,297,485
22 transactions · 21 stateful · 2026-07-29 08:35:23 UTC
Parallelism
73/100
Blocked
38%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,297,485 · 22 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
1w02w13w04w15w08w210w312w313w416w520w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd42a6b9…4c81
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x0226b774…a9ed
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xf942fbfe…90b7
0x34b655…2a6f
4 touches
1 conflict
0xee25bd64…191d
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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 0xfd42a6b911…394c81
Audit this contract →
← previous block·next block →recent activity