← previous blocknext block →recent activity
Analyzing
Block #91,189,678
23 transactions · 21 stateful · 2026-07-28 23:32:10 UTC
Parallelism
70/100
Blocked
38%
Avg conflicts / tx
0.91
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,189,678 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w07w09w113w114w215w317w421w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
10 touches
10 conflicts
0x0ab54c30…b88e
0x34b655…2a6f
8 touches
6 conflicts
0xcf7bbede…8ca1
0x34b655…2a6f
6 touches
3 conflicts
0x2d94ecd9…43db
0x34b655…2a6f
6 touches
3 conflicts
0xe48750bb…a4dd
0x34b655…2a6f
6 touches
3 conflicts
0x83dee4ed…fbad
0x34b655…2a6f
5 touches
3 conflicts
0x6925548b…81cc
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity