← previous blocknext block →recent activity
Analyzing
Block #87,587,008
21 transactions · 19 stateful · 2026-07-13 23:53:35 UTC
Parallelism
76/100
Blocked
53%
Avg conflicts / tx
1.29
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,587,008 · 21 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
2w03w14w05w16w08w19w210w311w412w217w318w320w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x571cb36d…3b3d
0x34b655…2a6f
10 touches
10 conflicts
0xfd77e6c1…264b
0x34b655…2a6f
10 touches
10 conflicts
0x73b261b4…0a79
0x34b655…2a6f
8 touches
6 conflicts
0x5febc2aa…f4d1
0x34b655…2a6f
6 touches
3 conflicts
0x63c900f4…2600
0x34b655…2a6f
6 touches
3 conflicts
0x5170a218…3a84
0xc8689a…ee79
6 touches
3 conflicts
0x1b2c54a1…5a76
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity