← previous blocknext block →recent activity
Analyzing
Block #99,477,172
21 transactions · 21 stateful · 2026-08-27 00:54:46 UTC
Parallelism
86/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,477,172 · 21 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
1w06w08w110w011w115w116w017w118w219w020w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe17ea3ec…0ab0
0x8964d7…10f8
6 touches
3 conflicts
0xe17ea3ec…0ab1
0x8964d7…10f8
6 touches
3 conflicts
0xe17ea3ec…0ab3
0x8964d7…10f8
6 touches
3 conflicts
0xfc8c8ece…f88d
0x8964d7…10f8
6 touches
3 conflicts
0xfc8c8ece…f88e
0x8964d7…10f8
6 touches
3 conflicts
0xfc8c8ece…f892
0x8964d7…10f8
6 touches
3 conflicts
0xfc8c8ece…f891
0x8964d7…10f8
6 touches
3 conflicts
0xfc8c8ece…f894
0x8964d7…10f8
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 0xe17ea3ecf3…620ab0
Audit this contract →
← previous block·next block →recent activity