← previous blocknext block →recent activity
Analyzing
Block #86,506,937
24 transactions · 22 stateful · 2026-07-08 23:30:01 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,506,937 · 24 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
1w03w14w05w07w18w212w013w114w117w020w321w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xa5ab7b8a…c97b
0x34b655…2a6f
6 touches
3 conflicts
0x36223362…c0ce
0x34b655…2a6f
4 touches
1 conflict
0x522e20b4…fbc4
0x34b655…2a6f
4 touches
1 conflict
0x64aaadbf…f9f3
0x34b655…2a6f
4 touches
1 conflict
0x65819aed…b748
0x34b655…2a6f
4 touches
1 conflict
0x79277877…6098
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4a4
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