← previous blocknext block →recent activity
Analyzing
Block #99,875,927
32 transactions · 31 stateful · 2026-08-28 10:35:12 UTC
Parallelism
66/100
Blocked
58%
Avg conflicts / tx
1.88
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #99,875,927 · 32 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
1w02w05w06w17w28w310w111w213w314w416w417w518w619w521w122w729w230w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fce7a05…d778
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x3d574fcf…275f
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x75286175…20dd
0x34b655…2a6f
10 touches
10 conflicts
0x39ccd26a…4654
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xb856d1a1…1f18
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
21 conflicts on slot 0x6fce7a0516…35d778
Audit this contract →
← previous block·next block →recent activity