← previous blocknext block →recent activity
Analyzing
Block #99,668,399
18 transactions · 18 stateful · 2026-08-27 17:04:36 UTC
Parallelism
78/100
Blocked
33%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,668,399 · 18 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
1w03w06w07w19w110w011w213w214w117w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x35b89cd8…5092
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x1b4318f0…78fb
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0xd563f3a1…94b1
0x34b655…2a6f
6 touches
3 conflicts
0x3b53436c…2ec3
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…642d
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 0x35b89cd80c…f05092
Audit this contract →
← previous block·next block →recent activity