← previous blocknext block →recent activity
Analyzing
Block #92,200,499
12 transactions · 12 stateful · 2026-08-01 12:19:18 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.58
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,200,499 · 12 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
1w02w03w14w05w16w27w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4717e60…2f9c
0x7b9256…1fb2
6 touches
3 conflicts
0x177211e2…1c2d
0x754704…b603
6 touches
3 conflicts
0xe1f61186…e2f8
0x754704…b603
6 touches
3 conflicts
0x00000000…0006
0x7b9256…1fb2
6 touches
3 conflicts
0x9cdb539b…a4b6
0x7b9256…1fb2
6 touches
3 conflicts
0x9cdb539b…a4b7
0x7b9256…1fb2
6 touches
3 conflicts
0x9cdb539b…a4b8
0x7b9256…1fb2
6 touches
3 conflicts
0xb4717e60…2f98
0x7b9256…1fb2
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: 0x7b9256fd…e21fb2
3 conflicts on slot 0xb4717e6058…952f9c
Audit this contract →
← previous block·next block →recent activity