← previous blocknext block →recent activity
Analyzing
Block #99,875,170
10 transactions · 10 stateful · 2026-08-28 10:31:23 UTC
Parallelism
70/100
Blocked
40%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,875,170 · 10 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
3w04w15w06w27w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x070b6f0e…ff7c
0x8964d7…10f8
6 touches
3 conflicts
0x070b6f0e…ff80
0x8964d7…10f8
6 touches
3 conflicts
0x070b6f0e…ff82
0x8964d7…10f8
6 touches
3 conflicts
0x2a07e64e…fe77
0x754704…b603
6 touches
3 conflicts
0x00000000…0008
0x8964d7…10f8
6 touches
3 conflicts
0x070b6f0e…ff7b
0x8964d7…10f8
6 touches
3 conflicts
0x070b6f0e…ff7f
0x8964d7…10f8
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
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
3 conflicts on slot 0x070b6f0e52…42ff7c
Audit this contract →
← previous block·next block →recent activity