← previous blocknext block →recent activity
Analyzing
Block #86,390,207
30 transactions · 25 stateful · 2026-07-08 10:30:04 UTC
Parallelism
87/100
Blocked
40%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,390,207 · 30 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w29w010w111w212w313w314w016w119w121w022w327w028w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x61435a6d…5321
0xd32edf…ff58
7 touches
6 conflicts
0x7523ad90…2ba5
0x34b655…2a6f
6 touches
3 conflicts
0x7c0bdc54…9dde
0x34b655…2a6f
6 touches
3 conflicts
0x924bac95…3f39
0x34b655…2a6f
6 touches
3 conflicts
0xa1144aa9…7f67
0x34b655…2a6f
6 touches
3 conflicts
0xc0b9bd73…7f1c
0x34b655…2a6f
6 touches
3 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 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
6 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity