← previous blocknext block →recent activity
Analyzing
Block #99,882,999
17 transactions · 15 stateful · 2026-08-28 11:10:50 UTC
Parallelism
65/100
Blocked
40%
Avg conflicts / tx
0.59
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,882,999 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w08w19w210w311w012w115w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x23769ebc…c8ed
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x736b9166…5ea5
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x0f15f74f…8d71
0x34b655…2a6f
4 touches
1 conflict
0x1b62550e…f9a8
0x34b655…2a6f
4 touches
1 conflict
0x247cfb80…cca8
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 0x23769ebc9a…0ec8ed
Audit this contract →
← previous block·next block →recent activity