← previous blocknext block →recent activity
Analyzing
Block #100,144,519
24 transactions · 21 stateful · 2026-08-29 09:08:05 UTC
Parallelism
58/100
Blocked
57%
Avg conflicts / tx
1.58
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #100,144,519 · 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
1w02w14w25w36w07w111w212w313w414w515w618w720w822w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeab71d04…e42a
0x34b655…2a6f
14 touches
21 conflicts
0x5ed1f9d0…fc7f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
6 touches
3 conflicts
0x0a6cb118…4ca8
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x5655f5c3…6b75
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 0xeab71d04cf…a6e42a
Audit this contract →
← previous block·next block →recent activity