← previous blocknext block →recent activity
Analyzing
Block #87,664,860
30 transactions · 25 stateful · 2026-07-14 08:34:03 UTC
Parallelism
83/100
Blocked
40%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,664,860 · 30 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w18w09w110w211w313w214w019w420w221w127w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x6e83a321…33a2
0x34b655…2a6f
6 touches
3 conflicts
0x94ba9c4a…41d8
0x34b655…2a6f
6 touches
3 conflicts
0x183c10a3…2e0a
0x34b655…2a6f
6 touches
3 conflicts
0x5bf44783…6166
0x34b655…2a6f
6 touches
3 conflicts
0x3a51d8ed…0c97
0x34b655…2a6f
4 touches
1 conflict
0x3b8c6a19…80d9
0x34b655…2a6f
4 touches
1 conflict
0x56ea7d7d…445a
0x34b655…2a6f
4 touches
1 conflict
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity