← previous blocknext block →recent activity
Analyzing
Block #86,958,309
24 transactions · 23 stateful · 2026-07-11 01:49:02 UTC
Parallelism
67/100
Blocked
57%
Avg conflicts / tx
1.71
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,958,309 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w16w27w38w49w510w612w313w414w116w217w320w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0x04105a34…6eea
0x34b655…2a6f
8 touches
6 conflicts
0x89c7ec3b…85ba
0x34b655…2a6f
8 touches
6 conflicts
0xb06917e8…6985
0x34b655…2a6f
8 touches
6 conflicts
0xc0b9bd73…7f1c
0x34b655…2a6f
8 touches
6 conflicts
0xf58f4849…c7c7
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xc7a15219…7745
0xa6afd3…d132
8 touches
6 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
21 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity