← previous blocknext block →recent activity
Analyzing
Block #86,308,100
17 transactions · 14 stateful · 2026-07-08 01:21:27 UTC
Parallelism
82/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,308,100 · 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
1w02w15w07w010w111w212w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x408e66bb…3d6b
0x34b655…2a6f
4 touches
1 conflict
0xacd1b162…bee6
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0xc5a1b2fe…5369
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x9c32afed…5d7c
0x40c49f…2af0
3 touches
1 conflict
0x65903ef9…2567
0x34b655…2a6f
2 touches
0 conflicts
0x7f9910cc…0f99
0x34b655…2a6f
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
1 conflict on slot 0x408e66bba7…d43d6b
Audit this contract →
← previous block·next block →recent activity