← previous blocknext block →recent activity
Analyzing
Block #99,660,256
23 transactions · 21 stateful · 2026-08-27 16:23:36 UTC
Parallelism
52/100
Blocked
67%
Avg conflicts / tx
2.26
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #99,660,256 · 23 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w36w39w410w515w116w518w621w922w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x25bd380f…a658
0x34b655…2a6f
10 touches
10 conflicts
0x886db264…846e
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xd2435a6c…621f
0x34b655…2a6f
6 touches
3 conflicts
0xea2a1d1b…4115
0x34b655…2a6f
6 touches
3 conflicts
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
28 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity