← previous blocknext block →recent activity
Analyzing
Block #99,879,707
19 transactions · 19 stateful · 2026-08-28 10:54:15 UTC
Parallelism
84/100
Blocked
32%
Avg conflicts / tx
0.37
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,879,707 · 19 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
3w04w18w09w110w011w112w214w015w117w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0008
0x8964d7…10f8
6 touches
3 conflicts
0x0d541617…868f
0x8964d7…10f8
6 touches
3 conflicts
0x0d541617…8690
0x8964d7…10f8
6 touches
3 conflicts
0x0d541617…8692
0x8964d7…10f8
6 touches
3 conflicts
0xb1ed0d3e…89ab
0x8964d7…10f8
6 touches
3 conflicts
0xb1ed0d3e…89ac
0x8964d7…10f8
6 touches
3 conflicts
0xb1ed0d3e…89af
0x8964d7…10f8
6 touches
3 conflicts
0xb1ed0d3e…89b0
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 0x0000000000…000008
Audit this contract →
← previous block·next block →recent activity