← previous blocknext block →recent activity
Analyzing
Block #86,628,351
31 transactions · 29 stateful · 2026-07-09 13:03:04 UTC
Parallelism
65/100
Blocked
66%
Avg conflicts / tx
1.97
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #86,628,351 · 31 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w05w16w07w18w212w013w014w215w116w117w218w119w223w324w425w526w628w829w930w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xa08f40b2…9a93
0x34b655…2a6f
14 touches
21 conflicts
0xefcdf197…96a2
0x34b655…2a6f
8 touches
6 conflicts
0x7ce93f3d…b70e
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x89c7ec3b…85ba
0x34b655…2a6f
6 touches
3 conflicts
0xc0eb79d1…29a4
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1a9
0xb1dbf0…c0d3
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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity