← previous blocknext block →recent activity
Analyzing
Block #100,227,616
24 transactions · 17 stateful · 2026-08-29 16:06:22 UTC
Parallelism
58/100
Blocked
71%
Avg conflicts / tx
1.79
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #100,227,616 · 24 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w19w210w211w314w415w516w618w721w722w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3ead1ba2…29f5
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x7aad02c6…b979
0x34b655…2a6f
8 touches
6 conflicts
0x3dae5ee1…721b
0x34b655…2a6f
6 touches
3 conflicts
0xb20094ed…0fef
0x34b655…2a6f
6 touches
3 conflicts
0x5b6af007…0f35
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
15 conflicts on slot 0x3ead1ba29e…bf29f5
Audit this contract →
← previous block·next block →recent activity