← previous blocknext block →recent activity
Analyzing
Block #99,985,803
23 transactions · 20 stateful · 2026-08-28 19:48:51 UTC
Parallelism
65/100
Blocked
40%
Avg conflicts / tx
0.78
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,985,803 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w010w011w112w213w314w417w518w521w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaef85d8c…963b
0x34b655…2a6f
10 touches
10 conflicts
0xf06fce24…887d
0x34b655…2a6f
10 touches
10 conflicts
0x6dedaff6…161b
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x7d499bce…b0ea
0x34b655…2a6f
8 touches
6 conflicts
0xa5977596…ddee
0x34b655…2a6f
8 touches
6 conflicts
0x07bb3f5a…617e
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0xaef85d8ceb…ae963b
Audit this contract →
← previous block·next block →recent activity