← previous blocknext block →recent activity
Analyzing
Block #92,188,937
18 transactions · 17 stateful · 2026-08-01 11:21:09 UTC
Parallelism
72/100
Blocked
41%
Avg conflicts / tx
0.78
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,188,937 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w16w27w08w19w210w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaa060c3d…9cd0
0x7b9256…1fb2
10 touches
10 conflicts
0xe1f61186…e2f8
0x754704…b603
10 touches
10 conflicts
0x00000000…0006
0x7b9256…1fb2
10 touches
10 conflicts
0xaa060c3d…9ccc
0x7b9256…1fb2
10 touches
10 conflicts
0xaa060c3d…9ccd
0x7b9256…1fb2
10 touches
10 conflicts
0xe01fcf41…45c3
0x7b9256…1fb2
10 touches
10 conflicts
0xe01fcf41…45c4
0x7b9256…1fb2
10 touches
10 conflicts
0xe01fcf41…45c2
0x7b9256…1fb2
10 touches
10 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
10 conflicts on slot 0xaa060c3dde…fe9cd0
Audit this contract →
← previous block·next block →recent activity