← previous blocknext block →recent activity
Analyzing
Block #86,613,345
17 transactions · 13 stateful · 2026-07-09 11:22:53 UTC
Parallelism
76/100
Blocked
31%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,613,345 · 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
5w06w17w28w311w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x922c7ebd…6600
0xc8689a…ee79
4 touches
1 conflict
0xc368d7fd…aaec
0x34b655…2a6f
4 touches
1 conflict
0xc435a04a…e025
0x34b655…2a6f
4 touches
1 conflict
0xcc3f7ee8…7924
0x34b655…2a6f
4 touches
1 conflict
0xef69c169…da9c
0x34b655…2a6f
4 touches
1 conflict
0xf7e59d30…11dd
0x34b655…2a6f
4 touches
1 conflict
0xfb4cb196…8c4a
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
6 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity