← previous blocknext block →recent activity
Analyzing
Block #86,945,440
10 transactions · 8 stateful · 2026-07-11 00:23:05 UTC
Parallelism
60/100
Blocked
50%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,945,440 · 10 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
2w04w15w26w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e303d0b…01bb
0x34b655…2a6f
8 touches
6 conflicts
0xd58e5c6b…7188
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x20067ecb…0e41
0x34b655…2a6f
4 touches
1 conflict
0x5f43f2bc…e94f
0x34b655…2a6f
4 touches
1 conflict
0x5f72d58f…c445
0x34b655…2a6f
2 touches
0 conflicts
0xbe5c8b52…88bc
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 0x6e303d0b67…b801bb
Audit this contract →
← previous block·next block →recent activity