← previous blocknext block →recent activity
Analyzing
Block #87,689,913
29 transactions · 28 stateful · 2026-07-14 11:21:28 UTC
Parallelism
62/100
Blocked
68%
Avg conflicts / tx
1.9
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #87,689,913 · 29 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w06w17w28w09w110w211w312w413w514w617w219w423w125w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
8 touches
6 conflicts
0x10b7971b…3ba4
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad06
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad07
0x34b655…2a6f
8 touches
6 conflicts
0x2fdfa032…139c
0x34b655…2a6f
8 touches
6 conflicts
0x4203ff9b…38e2
0x34b655…2a6f
8 touches
6 conflicts
0x4e3abeff…18eb
0x34b655…2a6f
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