← previous blocknext block →recent activity
Analyzing
Block #86,657,478
21 transactions · 18 stateful · 2026-07-09 16:19:01 UTC
Parallelism
62/100
Blocked
44%
Avg conflicts / tx
1.1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,657,478 · 21 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w37w411w013w518w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x0f13d630…5be3
0x34b655…2a6f
4 touches
1 conflict
0x250c8181…eef2
0x34b655…2a6f
4 touches
1 conflict
0x4e460439…5ba2
0x34b655…2a6f
4 touches
1 conflict
0x5fee1ba0…2520
0x34b655…2a6f
4 touches
1 conflict
0x6e688441…65ee
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
10 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity