← previous blocknext block →recent activity
Analyzing
Block #99,112,316
10 transactions · 10 stateful · 2026-08-25 18:18:20 UTC
Parallelism
70/100
Blocked
30%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,112,316 · 10 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
1w03w04w06w17w29w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x23c1dd54…8fdf
0x34b655…2a6f
6 touches
3 conflicts
0xce60df54…c3e8
0x34b655…2a6f
4 touches
1 conflict
0x6d5d1fb5…86a7
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x39ccd26a…4654
0x34b655…2a6f
4 touches
1 conflict
0xa7f7a563…4504
0x34b655…2a6f
2 touches
0 conflicts
0xb7e8b0c4…dec3
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
3 conflicts on slot 0x23c1dd540a…688fdf
Audit this contract →
← previous block·next block →recent activity