← previous blocknext block →recent activity
Analyzing
Block #90,879,603
23 transactions · 23 stateful · 2026-07-27 21:31:22 UTC
Parallelism
83/100
Blocked
39%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,879,603 · 23 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
1w03w04w15w26w37w39w010w111w212w313w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x11b69a7e…334e
0x01bff4…1071
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x33d4fbe3…a782
0x34b655…2a6f
6 touches
3 conflicts
0x07b86c51…cdae
0x2a68ba…90c5
6 touches
3 conflicts
0x0c7a00d5…7de0
0x851145…3f07
6 touches
3 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
6 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity