← previous blocknext block →recent activity
Analyzing
Block #99,307,918
18 transactions · 17 stateful · 2026-08-26 10:42:34 UTC
Parallelism
78/100
Blocked
53%
Avg conflicts / tx
0.72
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,307,918 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w18w09w210w111w212w313w115w217w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5a1b40e…5a12
0x34b655…2a6f
8 touches
6 conflicts
0x8ff85b19…dde0
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xf15273a1…2c52
0x34b655…2a6f
6 touches
3 conflicts
0x0dd3d3cd…7281
0x34b655…2a6f
6 touches
3 conflicts
0x42e5184f…4e8b
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7eb26548…8907
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
6 conflicts on slot 0xf5a1b40e1e…345a12
Audit this contract →
← previous block·next block →recent activity