← previous blocknext block →recent activity
Analyzing
Block #86,245,726
22 transactions · 20 stateful · 2026-07-07 18:25:03 UTC
Parallelism
73/100
Blocked
40%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,245,726 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w07w212w013w114w217w218w319w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xa6b89ebb…a66e
0x34b655…2a6f
8 touches
6 conflicts
0x1e9a8e72…7138
0x43cf54…7777
6 touches
3 conflicts
0x62fb2b24…4921
0x34b655…2a6f
4 touches
1 conflict
0x68c07cb9…ae14
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x83dee4ed…fbad
0x34b655…2a6f
4 touches
1 conflict
0x9b3a3ec5…17d5
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity