← previous blocknext block →recent activity
Analyzing
Block #87,663,849
20 transactions · 18 stateful · 2026-07-14 08:27:17 UTC
Parallelism
80/100
Blocked
28%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,663,849 · 20 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
1w05w06w110w011w112w213w114w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42c7fd6d…fc6c
0x34b655…2a6f
8 touches
6 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x2eb81c77…3c82
0x34b655…2a6f
4 touches
1 conflict
0x3646c884…13db
0x34b655…2a6f
4 touches
1 conflict
0x3b03c1f0…4921
0x34b655…2a6f
4 touches
1 conflict
0x55cf4758…265c
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
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 0x42c7fd6d32…0afc6c
Audit this contract →
← previous block·next block →recent activity