← previous blocknext block →recent activity
Analyzing
Block #100,162,240
25 transactions · 25 stateful · 2026-08-29 10:37:18 UTC
Parallelism
56/100
Blocked
56%
Avg conflicts / tx
2.12
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #100,162,240 · 25 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
1w02w13w24w05w07w19w010w113w214w315w417w518w119w620w723w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x24bb46f7…3853
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xcc9fa93a…f523
0x34b655…2a6f
8 touches
6 conflicts
0x8f267c0d…ebba
0x34b655…2a6f
8 touches
6 conflicts
0x10a5a231…be40
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
36 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity