← previous blocknext block →recent activity
Analyzing
Block #86,057,879
21 transactions · 17 stateful · 2026-07-06 21:31:06 UTC
Parallelism
81/100
Blocked
41%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,057,879 · 21 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
1w03w04w05w16w19w010w111w212w114w315w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2ba301a…ca6d
0x34b655…2a6f
6 touches
3 conflicts
0xd8bc53a3…c2fe
0x34b655…2a6f
6 touches
3 conflicts
0x91ff239c…e07b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x76ed8777…1e5f
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 0xf2ba301a68…c4ca6d
Audit this contract →
← previous block·next block →recent activity