← previous blocknext block →recent activity
Analyzing
Block #91,110,361
18 transactions · 16 stateful · 2026-07-28 16:53:09 UTC
Parallelism
78/100
Blocked
38%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,110,361 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w06w19w210w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x217bd767…b79e
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xa5420e1f…3788
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x2d651956…12e8
0x34b655…2a6f
4 touches
1 conflict
0xbb8bef08…cbbd
0x065c9d…c394
4 touches
1 conflict
0x1062ca99…dc10
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
3 conflicts on slot 0x217bd767aa…4fb79e
Audit this contract →
← previous block·next block →recent activity