← previous blocknext block →recent activity
Analyzing
Block #86,804,997
22 transactions · 20 stateful · 2026-07-10 08:44:05 UTC
Parallelism
73/100
Blocked
35%
Avg conflicts / tx
0.82
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,804,997 · 22 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
3w04w17w08w19w212w313w215w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdfc58aa8…e1df
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0xc2db6e7a…d074
0x34b655…2a6f
8 touches
6 conflicts
0xd8eed7e0…c96e
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x4d94760c…2bdd
0x34b655…2a6f
4 touches
1 conflict
0x548145a9…cfce
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 0xdfc58aa8cc…17e1df
Audit this contract →
← previous block·next block →recent activity