← previous blocknext block →recent activity
Analyzing
Block #87,668,308
25 transactions · 23 stateful · 2026-07-14 08:57:04 UTC
Parallelism
60/100
Blocked
48%
Avg conflicts / tx
1.24
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #87,668,308 · 25 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w48w59w617w723w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x1dd79365…4bab
0x34b655…2a6f
8 touches
6 conflicts
0x7ee6007b…fd68
0x34b655…2a6f
8 touches
6 conflicts
0x08330b36…ae29
0x34b655…2a6f
8 touches
6 conflicts
0x458ba337…6134
0x34b655…2a6f
8 touches
6 conflicts
0x4e1ce17e…98a7
0x34b655…2a6f
8 touches
6 conflicts
0xcffc8fcf…ff81
0x34b655…2a6f
8 touches
6 conflicts
0x5170a218…3a84
0xc8689a…ee79
8 touches
6 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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity