← previous blocknext block →recent activity
Analyzing
Block #86,834,220
19 transactions · 15 stateful · 2026-07-10 11:59:36 UTC
Parallelism
84/100
Blocked
27%
Avg conflicts / tx
0.32
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,834,220 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w06w17w210w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc7f6a3f…67a2
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xb1b21ea8…d790
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xea559e7b…41f4
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x3eede796…d745
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
3 conflicts on slot 0xcc7f6a3fd0…d167a2
Audit this contract →
← previous block·next block →recent activity