← previous blocknext block →recent activity
Analyzing
Block #92,079,467
21 transactions · 20 stateful · 2026-08-01 02:10:36 UTC
Parallelism
81/100
Blocked
35%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,079,467 · 21 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
3w04w16w09w110w011w112w213w314w216w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8c1c05a…b2cb
0x7b9256…1fb2
8 touches
6 conflicts
0x69b5aab5…d56c
0x7b9256…1fb2
8 touches
6 conflicts
0xe8c1c05a…b2ca
0x7b9256…1fb2
8 touches
6 conflicts
0x177211e2…1c2d
0x754704…b603
8 touches
6 conflicts
0xe1f61186…e2f8
0x754704…b603
8 touches
6 conflicts
0x00000000…0006
0x7b9256…1fb2
8 touches
6 conflicts
0x69b5aab5…d56b
0x7b9256…1fb2
8 touches
6 conflicts
0xe8c1c05a…b2ce
0x7b9256…1fb2
8 touches
6 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
6 conflicts on slot 0xe8c1c05ac2…65b2cb
Audit this contract →
← previous block·next block →recent activity