← previous blocknext block →recent activity
Analyzing
Block #85,994,009
33 transactions · 23 stateful · 2026-07-06 14:24:34 UTC
Parallelism
88/100
Blocked
39%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,994,009 · 33 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
2w05w17w28w110w212w016w017w119w325w226w329w030w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a2f9a36…fb4a
0xfa32f9…f3f0
8 touches
6 conflicts
0x99f666e3…b2a2
0x3bd359…433a
8 touches
6 conflicts
0x9194f4a3…10b8
0x754704…b603
8 touches
6 conflicts
0x00000000…0000
0xfa32f9…f3f0
8 touches
6 conflicts
0x00000000…0001
0xfa32f9…f3f0
8 touches
6 conflicts
0xa9b2b7fa…c060
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0x91945265…e58d
0x1b6862…e19c
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: 0xfa32f9ec…fef3f0
6 conflicts on slot 0x8a2f9a362c…60fb4a
Audit this contract →
← previous block·next block →recent activity