← previous blocknext block →recent activity
Analyzing
Block #86,387,893
19 transactions · 18 stateful · 2026-07-08 10:14:38 UTC
Parallelism
74/100
Blocked
50%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,387,893 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w18w09w110w111w212w013w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95d6e198…f79c
0x34b655…2a6f
6 touches
3 conflicts
0xd99c922e…5ca0
0x34b655…2a6f
6 touches
3 conflicts
0xecc08a94…8c86
0xd32edf…ff58
5 touches
3 conflicts
0xed8e1429…64f4
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4abfb389…18f4
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 0x95d6e1989e…e0f79c
Audit this contract →
← previous block·next block →recent activity