← previous blocknext block →recent activity
Analyzing
Block #87,785,316
45 transactions · 34 stateful · 2026-07-14 22:00:02 UTC
Parallelism
64/100
Blocked
68%
Avg conflicts / tx
2.33
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,785,316 · 45 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w38w09w110w011w120w221w322w423w525w729w731w932w1033w440w1142w1343w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
20 touches
45 conflicts
0x0dd44476…ef40
0x34b655…2a6f
20 touches
45 conflicts
0x55c2c22c…0474
0x34b655…2a6f
14 touches
21 conflicts
0x92385428…6941
0x34b655…2a6f
14 touches
21 conflicts
0x8b87ece6…3353
0x34b655…2a6f
12 touches
15 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0xa84ac543…8b65
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 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
45 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity