← previous blocknext block →recent activity
Analyzing
Block #87,592,658
16 transactions · 16 stateful · 2026-07-14 00:31:23 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
1.63
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,592,658 · 16 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w36w49w011w512w614w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd93edb3f…94ec
0x34b655…2a6f
14 touches
21 conflicts
0x2fade833…5de4
0x34b655…2a6f
10 touches
10 conflicts
0x34d95d94…3a16
0x34b655…2a6f
10 touches
10 conflicts
0x53bddbe8…2e5e
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x875164c2…f8a2
0x34b655…2a6f
10 touches
10 conflicts
0x167de262…f61f
0x34b655…2a6f
10 touches
10 conflicts
0x9599eb41…b5d6
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
21 conflicts on slot 0xd93edb3f20…0394ec
Audit this contract →
← previous block·next block →recent activity