← previous blocknext block →recent activity
Analyzing
Block #86,835,300
20 transactions · 16 stateful · 2026-07-10 12:06:49 UTC
Parallelism
70/100
Blocked
44%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,835,300 · 20 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
5w06w17w28w39w013w114w118w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4aa41e0…f123
0x34b655…2a6f
12 touches
15 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
8 touches
6 conflicts
0x63c900f4…2600
0x34b655…2a6f
8 touches
6 conflicts
0x7523ad90…2ba5
0x34b655…2a6f
8 touches
6 conflicts
0x851ff3c1…1b15
0x34b655…2a6f
8 touches
6 conflicts
0x9f40a209…1193
0x34b655…2a6f
8 touches
6 conflicts
0xc0b9bd73…7f1c
0x34b655…2a6f
8 touches
6 conflicts
0xedf4636f…b2a2
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
15 conflicts on slot 0xb4aa41e0a7…88f123
Audit this contract →
← previous block·next block →recent activity