← previous blocknext block →recent activity
Analyzing
Block #99,983,352
20 transactions · 19 stateful · 2026-08-28 19:36:30 UTC
Parallelism
80/100
Blocked
32%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,983,352 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w06w07w18w210w111w114w315w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcdd58ff…0711
0x34b655…2a6f
8 touches
6 conflicts
0x203a33b5…86c2
0x34b655…2a6f
8 touches
6 conflicts
0x36126dcb…ca1e
0x34b655…2a6f
6 touches
3 conflicts
0x65ddf9c4…2a1e
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x6676e4f3…6a9e
0x851145…3f07
4 touches
1 conflict
0x2d071de0…c86e
0x34b655…2a6f
4 touches
1 conflict
0x90a021f0…f922
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 0xbcdd58ff98…970711
Audit this contract →
← previous block·next block →recent activity