← previous blocknext block →recent activity
Analyzing
Block #86,709,841
18 transactions · 12 stateful · 2026-07-09 22:08:24 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,709,841 · 18 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
1w02w13w24w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x8a35acfb…d1aa
0xb1dbf0…c0d3
4 touches
1 conflict
0x6fdc73d3…9853
0xb1dbf0…c0d3
3 touches
1 conflict
0x8a35acfb…d1ab
0xb1dbf0…c0d3
3 touches
1 conflict
0xd040d680…4b05
0xb1dbf0…c0d3
3 touches
1 conflict
0x790f5479…fb39
0x40c49f…2af0
2 touches
0 conflicts
0xff99f5be…16df
0x40c49f…2af0
2 touches
0 conflicts
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity