← previous blocknext block →recent activity
Analyzing
Block #99,080,696
11 transactions · 10 stateful · 2026-08-25 15:39:05 UTC
Parallelism
64/100
Blocked
50%
Avg conflicts / tx
0.73
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,080,696 · 11 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
1w02w13w04w16w28w310w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x050347f0…d00f
0x34b655…2a6f
6 touches
3 conflicts
0xee757899…302b
0x34b655…2a6f
6 touches
3 conflicts
0xb82f494f…db33
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x845ec8b0…c1af
0x34b655…2a6f
6 touches
3 conflicts
0x9e1c65d0…77a3
0x34b655…2a6f
6 touches
3 conflicts
0x7c82b710…e9a9
0x34b655…2a6f
4 touches
1 conflict
0x02690385…0928
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 0x050347f009…0ad00f
Audit this contract →
← previous block·next block →recent activity