← previous blocknext block →recent activity
Analyzing
Block #86,507,174
33 transactions · 25 stateful · 2026-07-08 23:31:36 UTC
Parallelism
79/100
Blocked
36%
Avg conflicts / tx
0.64
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,507,174 · 33 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w214w015w317w018w119w226w327w428w529w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60c7217a…8c94
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xa7013be2…c0a8
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x961cd6bb…b3ac
0xd32edf…ff58
5 touches
3 conflicts
0x5bb46f6c…7693
0x34b655…2a6f
4 touches
1 conflict
0x63c900f4…2600
0x34b655…2a6f
4 touches
1 conflict
0x64a785e4…0110
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 0x60c7217a29…038c94
Audit this contract →
← previous block·next block →recent activity