← previous blocknext block →recent activity
Analyzing
Block #99,451,954
81 transactions · 57 stateful · 2026-08-26 22:47:49 UTC
Parallelism
78/100
Blocked
70%
Avg conflicts / tx
2.35
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #99,451,954 · 81 txs across 18 waves · depth 18
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w36w415w125w228w529w630w731w857w259w468w569w670w771w872w973w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
32 touches
120 conflicts
0xf3d10975…0d07
0x34b655…2a6f
30 touches
105 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
26 touches
78 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
26 touches
78 conflicts
0x6224c57b…57ba
0xd32edf…ff58
17 touches
36 conflicts
0x9fc6ea79…e2dc
0x34b655…2a6f
14 touches
21 conflicts
0x801a6e57…d85c
0x34b655…2a6f
14 touches
21 conflicts
0xfa324e43…889b
0x1b6862…e19c
12 touches
15 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
120 conflicts on slot 0xea02471df2…601542
Audit this contract →
← previous block·next block →recent activity