← previous blocknext block →recent activity
Analyzing
Block #92,063,858
16 transactions · 16 stateful · 2026-08-01 00:52:05 UTC
Parallelism
44/100
Blocked
56%
Avg conflicts / tx
2.31
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #92,063,858 · 16 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w37w48w59w610w711w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe7c23840…e413
0x7b9256…1fb2
18 touches
36 conflicts
0x177211e2…1c2d
0x754704…b603
18 touches
36 conflicts
0xe7c23840…e410
0x7b9256…1fb2
18 touches
36 conflicts
0xe7c23840…e40f
0x7b9256…1fb2
18 touches
36 conflicts
0xe1f61186…e2f8
0x754704…b603
18 touches
36 conflicts
0xabbdbb2d…5b9e
0x7b9256…1fb2
18 touches
36 conflicts
0xabbdbb2d…5b9d
0x7b9256…1fb2
18 touches
36 conflicts
0x00000000…0006
0x7b9256…1fb2
18 touches
36 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: 0x7b9256fd…e21fb2
36 conflicts on slot 0xe7c238405e…60e413
Audit this contract →
← previous block·next block →recent activity