← previous blocknext block →recent activity
Analyzing
Block #86,698,318
17 transactions · 17 stateful · 2026-07-09 20:51:31 UTC
Parallelism
82/100
Blocked
29%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,698,318 · 17 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
1w02w13w09w010w111w213w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51a9fa57…1dff
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x606bc50d…4c10
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x186903d3…3865
0x40c49f…2af0
2 touches
0 conflicts
0xafbddf7a…c6df
0x40c49f…2af0
2 touches
0 conflicts
0x213ee207…a151
0x69df8a…6292
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 0x51a9fa57f4…a61dff
Audit this contract →
← previous block·next block →recent activity