← previous blocknext block →recent activity
Analyzing
Block #99,960,411
21 transactions · 21 stateful · 2026-08-28 17:40:58 UTC
Parallelism
86/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,960,411 · 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
2w03w15w07w111w012w113w215w016w017w120w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0008
0x8964d7…10f8
4 touches
1 conflict
0x79a5f825…cf53
0x8964d7…10f8
4 touches
1 conflict
0x79a5f825…cf54
0x8964d7…10f8
4 touches
1 conflict
0x79a5f825…cf57
0x8964d7…10f8
4 touches
1 conflict
0x79a5f825…cf58
0x8964d7…10f8
4 touches
1 conflict
0x79a5f825…cf5a
0x8964d7…10f8
4 touches
1 conflict
0x62910921…3016
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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: 0x8964d7c9…5b10f8
1 conflict on slot 0x0000000000…000008
Audit this contract →
← previous block·next block →recent activity