← previous blocknext block →recent activity
Analyzing
Block #86,658,532
25 transactions · 20 stateful · 2026-07-09 16:26:03 UTC
Parallelism
84/100
Blocked
35%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,658,532 · 25 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
1w03w14w26w07w110w011w112w213w320w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1a8
0xb1dbf0…c0d3
6 touches
3 conflicts
0x6c68ddc9…d106
0xb1dbf0…c0d3
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0ff1ee46…0c08
0x34b655…2a6f
4 touches
1 conflict
0x5a15f3ca…4138
0x34b655…2a6f
4 touches
1 conflict
0x63ee66d8…e145
0x34b655…2a6f
4 touches
1 conflict
0x6cad9553…19d1
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