← previous blocknext block →recent activity
Analyzing
Block #99,875,771
24 transactions · 22 stateful · 2026-08-28 10:34:25 UTC
Parallelism
79/100
Blocked
50%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,875,771 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w07w08w19w212w113w214w116w317w018w119w220w321w022w123w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x15413337…2a40
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0xb856d1a1…1f18
0x34b655…2a6f
8 touches
6 conflicts
0x89999c15…fdac
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x09106a95…1467
0x33176b…e078
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 0x15413337e4…272a40
Audit this contract →
← previous block·next block →recent activity