← previous blocknext block →recent activity
Analyzing
Block #100,789,072
75 transactions · 63 stateful · 2026-08-31 15:14:57 UTC
Parallelism
77/100
Blocked
75%
Avg conflicts / tx
2.31
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #100,789,072 · 75 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w07w08w19w212w313w114w115w016w117w018w119w223w624w237w338w439w342w445w146w755w159w262w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0xea02471d…1542
0x34b655…2a6f
18 touches
36 conflicts
0xf3d10975…0d07
0x34b655…2a6f
18 touches
36 conflicts
0x675ee4ca…2455
0x34b655…2a6f
12 touches
15 conflicts
0xdc9915b5…542c
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x38f05285…8dab
0xd32edf…ff58
11 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
45 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity