← previous blocknext block →recent activity
Analyzing
Block #99,170,471
35 transactions · 29 stateful · 2026-08-25 23:11:00 UTC
Parallelism
83/100
Blocked
31%
Avg conflicts / tx
0.46
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,170,471 · 35 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w112w213w314w415w016w117w428w530w031w133w034w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f88acf6…d385
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x109d8a52…a7b7
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x6713b018…05f3
0x34b655…2a6f
6 touches
3 conflicts
0x5883907e…2fd1
0x34b655…2a6f
4 touches
1 conflict
0x64275949…d698
0x34b655…2a6f
4 touches
1 conflict
0x6d787177…e955
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 0x5f88acf675…35d385
Audit this contract →
← previous block·next block →recent activity