← previous blocknext block →recent activity
Analyzing
Block #86,281,693
18 transactions · 15 stateful · 2026-07-07 22:25:09 UTC
Parallelism
78/100
Blocked
20%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,281,693 · 18 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
2w03w14w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc85f42b6…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xec0e0220…cb90
0x34b655…2a6f
6 touches
3 conflicts
0x79e8f935…c3b6
0x34b655…2a6f
6 touches
3 conflicts
0xc7178f14…9efb
0x34b655…2a6f
6 touches
3 conflicts
0xcd176877…2c75
0x34b655…2a6f
4 touches
1 conflict
0x280bd9bd…f01d
0x34b655…2a6f
4 touches
1 conflict
0x05ca4d57…2eed
0x34b655…2a6f
4 touches
1 conflict
0x4abfb389…18f4
0x34b655…2a6f
2 touches
0 conflicts
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
6 conflicts on slot 0xc85f42b605…b36f23
Audit this contract →
← previous block·next block →recent activity