← previous blocknext block →recent activity
Analyzing
Block #92,059,619
12 transactions · 12 stateful · 2026-08-01 00:30:46 UTC
Parallelism
58/100
Blocked
50%
Avg conflicts / tx
1.08
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,059,619 · 12 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
2w04w05w16w27w38w49w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc94e6694…e6b3
0x7b9256…1fb2
10 touches
10 conflicts
0x177211e2…1c2d
0x754704…b603
10 touches
10 conflicts
0xe1f61186…e2f8
0x754704…b603
10 touches
10 conflicts
0xc94e6694…e6b0
0x7b9256…1fb2
10 touches
10 conflicts
0x7ee6ac95…d579
0x7b9256…1fb2
10 touches
10 conflicts
0x7ee6ac95…d578
0x7b9256…1fb2
10 touches
10 conflicts
0x00000000…0006
0x7b9256…1fb2
10 touches
10 conflicts
0xc94e6694…e6af
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 0xc94e66945e…3ce6b3
Audit this contract →
← previous block·next block →recent activity