← previous blocknext block →recent activity
Analyzing
Block #87,713,784
20 transactions · 18 stateful · 2026-07-14 14:01:21 UTC
Parallelism
75/100
Blocked
44%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,713,784 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w39w412w013w115w216w018w119w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xa558e115…fc88
0x34b655…2a6f
6 touches
3 conflicts
0xaa4b086b…58b5
0x34b655…2a6f
6 touches
3 conflicts
0xaae6463e…bfcc
0x34b655…2a6f
6 touches
3 conflicts
0xbf78ee7f…e7fd
0x34b655…2a6f
6 touches
3 conflicts
0xe09fa705…101e
0x34b655…2a6f
6 touches
3 conflicts
0xf5e8732e…adea
0x34b655…2a6f
6 touches
3 conflicts
0x4528594e…919a
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity