← previous blocknext block →recent activity
Analyzing
Block #87,616,427
21 transactions · 17 stateful · 2026-07-14 03:10:20 UTC
Parallelism
67/100
Blocked
53%
Avg conflicts / tx
0.9
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,616,427 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w310w011w412w513w616w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x745952b2…d90c
0x34b655…2a6f
8 touches
6 conflicts
0xd93edb3f…94ec
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x49f75237…44f4
0x34b655…2a6f
6 touches
3 conflicts
0x75b43fdd…8dc1
0x34b655…2a6f
6 touches
3 conflicts
0x91d48be7…e4e8
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x9599eb41…b5d6
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
6 conflicts on slot 0x745952b2a0…a6d90c
Audit this contract →
← previous block·next block →recent activity