← previous blocknext block →recent activity
Analyzing
Block #87,626,895
22 transactions · 20 stateful · 2026-07-14 04:20:20 UTC
Parallelism
82/100
Blocked
40%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,626,895 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w27w310w011w112w213w315w018w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x62cc9214…441b
0x34b655…2a6f
6 touches
3 conflicts
0xac388ba5…a800
0x34b655…2a6f
6 touches
3 conflicts
0xacb6de83…d893
0x34b655…2a6f
6 touches
3 conflicts
0x3cb8c8c3…22f4
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x6254804c…a03b
0x34b655…2a6f
6 touches
3 conflicts
0x98459f89…575d
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity