← previous blocknext block →recent activity
Analyzing
Block #92,759,332
24 transactions · 18 stateful · 2026-08-03 11:11:02 UTC
Parallelism
75/100
Blocked
39%
Avg conflicts / tx
0.54
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #92,759,332 · 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
1w03w15w27w09w111w212w313w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68caa37b…c795
0x34b655…2a6f
8 touches
6 conflicts
0x743061ce…a4ac
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xb6ea4726…5140
0x34b655…2a6f
6 touches
3 conflicts
0x7b80de04…86d1
0x34b655…2a6f
6 touches
3 conflicts
0x17c93766…889e
0x34b655…2a6f
4 touches
1 conflict
0x1bfab537…7bad
0x34b655…2a6f
4 touches
1 conflict
0x2921dcba…1433
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
6 conflicts on slot 0x68caa37b30…f7c795
Audit this contract →
← previous block·next block →recent activity