← previous blocknext block →recent activity
Analyzing
Block #86,332,043
17 transactions · 15 stateful · 2026-07-08 04:01:25 UTC
Parallelism
76/100
Blocked
27%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,332,043 · 17 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
5w07w08w110w014w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x96047c45…b64a
0x34b655…2a6f
5 touches
3 conflicts
0xfc578b53…9b1f
0xa6afd3…d132
4 touches
1 conflict
0x03d26443…fcc1
0x34b655…2a6f
4 touches
1 conflict
0x0acdb923…6eee
0x34b655…2a6f
4 touches
1 conflict
0x70ff9262…8d80
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
3 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity