← previous blocknext block →recent activity
Analyzing
Block #86,332,065
12 transactions · 10 stateful · 2026-07-08 04:01:34 UTC
Parallelism
67/100
Blocked
30%
Avg conflicts / tx
0.25
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,332,065 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w08w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f1bd077…2005
0x34b655…2a6f
4 touches
1 conflict
0x96047c45…b64a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9416
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9417
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x03d26443…fcc1
0x34b655…2a6f
4 touches
1 conflict
0x8eb0ac6b…a73a
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
1 conflict on slot 0x6f1bd0770e…6e2005
Audit this contract →
← previous block·next block →recent activity