← previous blocknext block →recent activity
Analyzing
Block #99,879,885
16 transactions · 15 stateful · 2026-08-28 10:55:09 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,879,885 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w07w08w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1ed0d3e…89b2
0x8964d7…10f8
4 touches
1 conflict
0x00000000…0008
0x8964d7…10f8
4 touches
1 conflict
0x0d541617…868f
0x8964d7…10f8
4 touches
1 conflict
0x0d541617…8690
0x8964d7…10f8
4 touches
1 conflict
0x0d541617…8692
0x8964d7…10f8
4 touches
1 conflict
0xb1ed0d3e…89ab
0x8964d7…10f8
4 touches
1 conflict
0xb1ed0d3e…89ac
0x8964d7…10f8
4 touches
1 conflict
0xb1ed0d3e…89af
0x8964d7…10f8
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: 0x8964d7c9…5b10f8
1 conflict on slot 0xb1ed0d3e18…2889b2
Audit this contract →
← previous block·next block →recent activity