← previous blocknext block →recent activity
Analyzing
Block #99,288,163
14 transactions · 11 stateful · 2026-08-26 09:03:12 UTC
Parallelism
79/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,288,163 · 14 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
5w06w07w18w09w210w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ab2f865…d113
0x34b655…2a6f
6 touches
3 conflicts
0xe283e878…7262
0x34b655…2a6f
6 touches
3 conflicts
0x86e2fc82…26c8
0x8964d7…10f8
4 touches
1 conflict
0x86e2fc82…26c1
0x8964d7…10f8
4 touches
1 conflict
0x86e2fc82…26c2
0x8964d7…10f8
4 touches
1 conflict
0x86e2fc82…26c5
0x8964d7…10f8
4 touches
1 conflict
0x86e2fc82…26c6
0x8964d7…10f8
4 touches
1 conflict
0x0ed7cc0b…ee52
0x34b655…2a6f
4 touches
1 conflict
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: Perpl
3 conflicts on slot 0x9ab2f865a4…81d113
Audit this contract →
← previous block·next block →recent activity