← previous blocknext block →recent activity
Analyzing
Block #87,628,391
23 transactions · 22 stateful · 2026-07-14 04:30:22 UTC
Parallelism
65/100
Blocked
45%
Avg conflicts / tx
1.48
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,628,391 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w08w19w210w311w412w518w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08330b36…ae29
0x34b655…2a6f
14 touches
21 conflicts
0xed59b1cd…8509
0x34b655…2a6f
12 touches
15 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x2697123c…8526
0x34b655…2a6f
10 touches
10 conflicts
0x5b145de0…367c
0xc8689a…ee79
10 touches
10 conflicts
0x4560e5a8…b741
0x34b655…2a6f
10 touches
10 conflicts
0x49f75237…44f4
0x34b655…2a6f
10 touches
10 conflicts
0xf04687a1…5ffa
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
21 conflicts on slot 0x08330b3687…a7ae29
Audit this contract →
← previous block·next block →recent activity