← previous blocknext block →recent activity
Analyzing
Block #86,612,838
23 transactions · 22 stateful · 2026-07-09 11:19:31 UTC
Parallelism
74/100
Blocked
41%
Avg conflicts / tx
0.61
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,612,838 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w28w112w213w314w417w319w320w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x3bdd71a2…b6eb
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x8eb0ac6b…a73a
0x34b655…2a6f
6 touches
3 conflicts
0x3e8c7016…0c69
0x34b655…2a6f
6 touches
3 conflicts
0xfb4cb196…8c4a
0x34b655…2a6f
4 touches
1 conflict
0x0f3016b9…e6d3
0x34b655…2a6f
4 touches
1 conflict
0x28653e24…7b35
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity