← previous blocknext block →recent activity
Analyzing
Block #86,238,476
22 transactions · 19 stateful · 2026-07-07 17:36:34 UTC
Parallelism
73/100
Blocked
42%
Avg conflicts / tx
0.77
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,238,476 · 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
1w05w06w19w210w313w115w217w319w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08330b36…ae29
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xbcdee322…f454
0xa6afd3…d132
8 touches
6 conflicts
0x006ee1d9…5485
0xa6afd3…d132
6 touches
3 conflicts
0x7e2d46e0…388c
0x34b655…2a6f
4 touches
1 conflict
0x9ae859db…2d84
0x34b655…2a6f
4 touches
1 conflict
0x9ffb63ac…ab50
0x34b655…2a6f
4 touches
1 conflict
0xbabe821d…939b
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 0x08330b3687…a7ae29
Audit this contract →
← previous block·next block →recent activity