← previous blocknext block →recent activity
Analyzing
Block #99,851,103
15 transactions · 14 stateful · 2026-08-28 08:30:00 UTC
Parallelism
80/100
Blocked
21%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,851,103 · 15 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
1w07w18w212w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee32a48d…4ecc
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x15698ac9…2a46
0x34b655…2a6f
4 touches
1 conflict
0x4c9c6299…75a6
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
2 touches
0 conflicts
0x1e1541ce…9e06
0x34b655…2a6f
2 touches
0 conflicts
0x271ab0bd…7594
0x34b655…2a6f
2 touches
0 conflicts
0x2999ebda…ce6c
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0xee32a48d5f…514ecc
Audit this contract →
← previous block·next block →recent activity