← previous blocknext block →recent activity
Analyzing
Block #86,444,336
15 transactions · 8 stateful · 2026-07-08 16:31:32 UTC
Parallelism
87/100
Blocked
13%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,444,336 · 15 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1664dd20…d2a9
0x34b655…2a6f
4 touches
1 conflict
0xdf64e5e6…75e8
0x34b655…2a6f
4 touches
1 conflict
0xd6d040d9…9ae3
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x000bde1a…e123
0x34b655…2a6f
2 touches
0 conflicts
0x157dbfb2…4089
0x34b655…2a6f
2 touches
0 conflicts
0x2ec96dbf…e1de
0x34b655…2a6f
2 touches
0 conflicts
0x51ffd098…59d4
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x1664dd204a…bcd2a9
Audit this contract →
← previous block·next block →recent activity