← previous blocknext block →recent activity
Analyzing
Block #87,662,359
36 transactions · 30 stateful · 2026-07-14 08:17:18 UTC
Parallelism
64/100
Blocked
67%
Avg conflicts / tx
2.42
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #87,662,359 · 36 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w07w18w09w110w211w312w413w514w615w716w817w918w1021w122w124w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
24 touches
66 conflicts
0x08330b36…ae29
0x34b655…2a6f
10 touches
10 conflicts
0x21c9fd73…dae4
0x34b655…2a6f
10 touches
10 conflicts
0x2d94ecd9…43db
0x34b655…2a6f
10 touches
10 conflicts
0x3c0c2f32…c3df
0x34b655…2a6f
10 touches
10 conflicts
0x05b1b07a…7a99
0x34b655…2a6f
10 touches
10 conflicts
0x648bb928…97f2
0x34b655…2a6f
10 touches
10 conflicts
0x75b43fdd…8dc1
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
66 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity