← previous blocknext block →recent activity
Analyzing
Block #99,479,881
23 transactions · 22 stateful · 2026-08-27 01:08:26 UTC
Parallelism
78/100
Blocked
41%
Avg conflicts / tx
0.87
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,479,881 · 23 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
3w04w15w26w07w18w19w212w013w114w317w018w419w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd814f518…f5b4
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x73eeaa45…8a53
0x40c49f…2af0
4 touches
1 conflict
0x6ca15e14…7be8
0x34b655…2a6f
4 touches
1 conflict
0x0ec34d4f…5fa1
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
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
10 conflicts on slot 0xd814f51828…c6f5b4
Audit this contract →
← previous block·next block →recent activity