← previous blocknext block →recent activity
Analyzing
Block #86,677,710
20 transactions · 18 stateful · 2026-07-09 18:34:00 UTC
Parallelism
70/100
Blocked
39%
Avg conflicts / tx
0.85
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,677,710 · 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
3w04w16w113w114w215w316w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xc55a9a20…89ac
0x34b655…2a6f
4 touches
1 conflict
0xe5f9a967…ee64
0x34b655…2a6f
4 touches
1 conflict
0xffd70256…bd99
0x34b655…2a6f
4 touches
1 conflict
0x1fc43cd8…0f26
0x34b655…2a6f
4 touches
1 conflict
0x40b18770…e631
0x34b655…2a6f
4 touches
1 conflict
0x43e15ca4…039d
0x34b655…2a6f
4 touches
1 conflict
0x5f251b96…6054
0x34b655…2a6f
4 touches
1 conflict
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity