← previous blocknext block →recent activity
Analyzing
Block #99,790,631
23 transactions · 23 stateful · 2026-08-28 03:24:02 UTC
Parallelism
78/100
Blocked
39%
Avg conflicts / tx
0.74
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,790,631 · 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
2w05w06w07w18w19w111w013w214w315w417w018w121w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x5da92df7…74b5
0x34b655…2a6f
6 touches
3 conflicts
0x08399ab6…0057
0x34b655…2a6f
6 touches
3 conflicts
0x230d0904…a656
0x34b655…2a6f
4 touches
1 conflict
0x339c92e7…1852
0x34b655…2a6f
4 touches
1 conflict
0x3b062f9f…76db
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity