← previous blocknext block →recent activity
Analyzing
Block #92,569,779
18 transactions · 16 stateful · 2026-08-02 19:16:29 UTC
Parallelism
78/100
Blocked
44%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,569,779 · 18 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
3w06w17w28w09w110w212w013w114w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xbb59cc25…7b48
0x968279…9342
6 touches
3 conflicts
0x30b70473…9295
0x968279…9342
6 touches
3 conflicts
0xbb59cc25…7b42
0x968279…9342
6 touches
3 conflicts
0xbb59cc25…7b43
0x968279…9342
6 touches
3 conflicts
0xbb59cc25…7b46
0x968279…9342
6 touches
3 conflicts
0xbb59cc25…7b47
0x968279…9342
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
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: Perpl
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity