← previous blocknext block →recent activity
Analyzing
Block #86,824,226
20 transactions · 19 stateful · 2026-07-10 10:52:47 UTC
Parallelism
65/100
Blocked
42%
Avg conflicts / tx
1.25
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,824,226 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w06w17w28w39w410w514w215w119w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d888c90…5479
0x34b655…2a6f
14 touches
21 conflicts
0x0f4cddfd…3085
0x34b655…2a6f
14 touches
21 conflicts
0xd1ec0dfd…ccc0
0xc8689a…ee79
12 touches
15 conflicts
0x01521950…6f17
0x34b655…2a6f
12 touches
15 conflicts
0x873b97ca…9f25
0x34b655…2a6f
12 touches
15 conflicts
0x9068a9bc…86ee
0x34b655…2a6f
12 touches
15 conflicts
0xb7a47e62…7963
0x34b655…2a6f
12 touches
15 conflicts
0xbca4de0c…577c
0x34b655…2a6f
12 touches
15 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 0x8d888c9003…aa5479
Audit this contract →
← previous block·next block →recent activity