← previous blocknext block →recent activity
Analyzing
Block #92,756,930
14 transactions · 13 stateful · 2026-08-03 10:58:57 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,756,930 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w08w19w211w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x306c8565…815c
0x968279…9342
6 touches
3 conflicts
0x00e113f5…7c34
0x968279…9342
6 touches
3 conflicts
0x00e113f5…7c35
0x968279…9342
6 touches
3 conflicts
0x00e113f5…7c36
0x968279…9342
6 touches
3 conflicts
0x00e113f5…7c37
0x968279…9342
6 touches
3 conflicts
0x306c8565…8155
0x968279…9342
6 touches
3 conflicts
0x306c8565…8156
0x968279…9342
6 touches
3 conflicts
0x306c8565…8159
0x968279…9342
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: 0x96827978…f09342
3 conflicts on slot 0x306c85655a…f8815c
Audit this contract →
← previous block·next block →recent activity