← previous blocknext block →recent activity
Analyzing
Block #99,935,323
19 transactions · 19 stateful · 2026-08-28 15:34:32 UTC
Parallelism
68/100
Blocked
32%
Avg conflicts / tx
0.68
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,935,323 · 19 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
4w05w07w08w19w210w011w112w013w314w417w018w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd6113c0f…0a4b
0x34b655…2a6f
6 touches
3 conflicts
0xe3c0e27d…456d
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x3b56f79b…310f
0x34b655…2a6f
4 touches
1 conflict
0x470b41f6…fc68
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x62910921…3016
0x34b655…2a6f
4 touches
1 conflict
0x6324ccc9…14fd
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 0xd6113c0f7f…b30a4b
Audit this contract →
← previous block·next block →recent activity