← previous blocknext block →recent activity
Analyzing
Block #99,491,376
13 transactions · 13 stateful · 2026-08-27 02:06:20 UTC
Parallelism
77/100
Blocked
23%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,491,376 · 13 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
6w08w09w110w212w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x36f538e5…4706
0x8964d7…10f8
6 touches
3 conflicts
0x6c3870ae…264a
0x8964d7…10f8
6 touches
3 conflicts
0x6c3870ae…264b
0x8964d7…10f8
6 touches
3 conflicts
0x6c3870ae…264d
0x8964d7…10f8
6 touches
3 conflicts
0x36f538e5…4702
0x8964d7…10f8
6 touches
3 conflicts
0x36f538e5…4705
0x8964d7…10f8
6 touches
3 conflicts
0x36f538e5…4707
0x8964d7…10f8
6 touches
3 conflicts
0x177211e2…1c2d
0x754704…b603
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: 0x8964d7c9…5b10f8
3 conflicts on slot 0x36f538e50d…a64706
Audit this contract →
← previous block·next block →recent activity