← previous blocknext block →recent activity
Analyzing
Block #86,388,410
19 transactions · 17 stateful · 2026-07-08 10:18:04 UTC
Parallelism
68/100
Blocked
47%
Avg conflicts / tx
1.11
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,388,410 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w412w514w015w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x96047c45…b64a
0x34b655…2a6f
12 touches
15 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
12 touches
15 conflicts
0x922c7ebd…6600
0xc8689a…ee79
10 touches
10 conflicts
0x727fbce7…0c80
0x34b655…2a6f
10 touches
10 conflicts
0x7523ad90…2ba5
0x34b655…2a6f
10 touches
10 conflicts
0x7c0bdc54…9dde
0x34b655…2a6f
10 touches
10 conflicts
0xa1144aa9…7f67
0x34b655…2a6f
10 touches
10 conflicts
0xa4e5e0c2…6e04
0x34b655…2a6f
10 touches
10 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
15 conflicts on slot 0x96047c45d5…89b64a
Audit this contract →
← previous block·next block →recent activity