← previous blocknext block →recent activity
Analyzing
Block #86,232,176
16 transactions · 13 stateful · 2026-07-07 16:54:31 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,232,176 · 16 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
1w02w03w16w09w110w113w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa86351b8…2c5a
0x34b655…2a6f
6 touches
3 conflicts
0xbcdee322…f454
0xa6afd3…d132
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xf06c2cf5…61bd
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x006ee1d9…5485
0xa6afd3…d132
4 touches
1 conflict
0x1616f80b…6c6e
0x34b655…2a6f
4 touches
1 conflict
0x182e11cf…8f19
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 0xa86351b861…d52c5a
Audit this contract →
← previous block·next block →recent activity