← previous blocknext block →recent activity
Analyzing
Block #86,687,054
19 transactions · 17 stateful · 2026-07-09 19:36:25 UTC
Parallelism
79/100
Blocked
35%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,687,054 · 19 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
2w05w09w110w111w212w216w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x312e4698…54c0
0x34b655…2a6f
4 touches
1 conflict
0x38a3bbfd…8269
0x34b655…2a6f
4 touches
1 conflict
0x3959d20b…8235
0x34b655…2a6f
4 touches
1 conflict
0x4bd1d7fb…b907
0x34b655…2a6f
4 touches
1 conflict
0x9385d07d…4829
0x34b655…2a6f
4 touches
1 conflict
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity