← previous blocknext block →recent activity
Analyzing
Block #87,639,177
25 transactions · 21 stateful · 2026-07-14 05:42:29 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
1.08
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #87,639,177 · 25 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w312w413w515w616w718w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x68b75835…d6f3
0x34b655…2a6f
8 touches
6 conflicts
0xa1571d54…ae41
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xb670a63e…ead8
0x34b655…2a6f
8 touches
6 conflicts
0x04c1786f…3ee6
0x34b655…2a6f
8 touches
6 conflicts
0xe734d3e3…8329
0x34b655…2a6f
8 touches
6 conflicts
0xfe01b93c…5865
0x34b655…2a6f
8 touches
6 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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity