← previous blocknext block →recent activity
Analyzing
Block #93,920,711
37 transactions · 36 stateful · 2026-08-07 12:33:03 UTC
Parallelism
73/100
Blocked
58%
Avg conflicts / tx
1.49
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #93,920,711 · 37 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w48w29w010w111w212w313w315w416w323w531w632w733w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51232c8c…f30c
0xe52b14…7230
12 touches
15 conflicts
0x51232c8c…f30e
0xe52b14…7230
12 touches
15 conflicts
0xf79df061…e005
0xe52b14…7230
12 touches
15 conflicts
0xf275b4ca…57b8
0xe52b14…7230
12 touches
15 conflicts
0xddbbd27c…57ce
0xe52b14…7230
12 touches
15 conflicts
0xa6e37efb…afc0
0xe52b14…7230
12 touches
15 conflicts
0x7e0be317…413d
0xd32edf…ff58
9 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 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: 0xe52b1424…bb7230
15 conflicts on slot 0x51232c8c1f…6df30c
Audit this contract →
← previous block·next block →recent activity