← previous blocknext block →recent activity
Analyzing
Block #99,329,044
19 transactions · 19 stateful · 2026-08-26 12:28:50 UTC
Parallelism
79/100
Blocked
53%
Avg conflicts / tx
0.68
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,329,044 · 19 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
1w02w13w04w05w16w27w19w211w212w213w214w318w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9ab93a0…f656
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x731d7308…fd26
0x34b655…2a6f
6 touches
3 conflicts
0x746bcce3…d0ce
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x3e6302c8…64f5
0x34b655…2a6f
4 touches
1 conflict
0x60a536a6…ef7a
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 0xb9ab93a0c0…6ff656
Audit this contract →
← previous block·next block →recent activity