← previous blocknext block →recent activity
Analyzing
Block #86,628,969
28 transactions · 23 stateful · 2026-07-09 13:07:11 UTC
Parallelism
82/100
Blocked
48%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,628,969 · 28 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
1w02w13w04w05w16w07w28w19w111w212w313w414w226w127w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x4a92f8…f3d6
10 touches
10 conflicts
0x0db0aaac…e94d
0x43cf54…7777
10 touches
10 conflicts
0x4a4c3d20…bd65
0x3bd359…433a
10 touches
10 conflicts
0x00000000…0001
0x4a92f8…f3d6
8 touches
6 conflicts
0x5504f74a…6874
0x43cf54…7777
6 touches
3 conflicts
0x00000000…0004
0x48c3bb…b17b
6 touches
3 conflicts
0xdd43be87…f667
0xe1c8b7…3022
6 touches
3 conflicts
0x44ed742f…63f5
0x3bd359…433a
6 touches
3 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: 0x4a92f8d9…13f3d6
10 conflicts on slot 0x0000000000…000000
Audit this contract →
← previous block·next block →recent activity