← previous blocknext block →recent activity
Analyzing
Block #87,661,839
20 transactions · 16 stateful · 2026-07-14 08:13:50 UTC
Parallelism
80/100
Blocked
56%
Avg conflicts / tx
0.8
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,661,839 · 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
1w02w03w15w16w19w211w312w113w214w119w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69ce640b…884a
0x34b655…2a6f
8 touches
6 conflicts
0xc514314c…1aa4
0x34b655…2a6f
6 touches
3 conflicts
0x944bfd2a…49f7
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xf8ceaa24…6e8e
0x851145…3f07
6 touches
3 conflicts
0x5060cdde…445d
0x34b655…2a6f
4 touches
1 conflict
0x5e3014f0…b4e1
0x34b655…2a6f
4 touches
1 conflict
0x5ece8f90…f4c5
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 0x69ce640b96…ed884a
Audit this contract →
← previous block·next block →recent activity