← previous blocknext block →recent activity
Analyzing
Block #99,080,573
17 transactions · 16 stateful · 2026-08-25 15:38:27 UTC
Parallelism
82/100
Blocked
38%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,080,573 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w08w19w110w113w114w216w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb82f494f…db33
0x34b655…2a6f
6 touches
3 conflicts
0x1bee5aea…5f61
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xccebf5c5…8759
0x34b655…2a6f
4 touches
1 conflict
0xccebf5c5…8758
0x34b655…2a6f
4 touches
1 conflict
0x00e21a9f…3583
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 0xb82f494f98…19db33
Audit this contract →
← previous block·next block →recent activity