← previous blocknext block →recent activity
Analyzing
Block #100,227,134
57 transactions · 45 stateful · 2026-08-29 16:03:57 UTC
Parallelism
72/100
Blocked
69%
Avg conflicts / tx
2.18
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #100,227,134 · 57 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w06w07w18w211w312w417w120w122w524w335w239w342w448w749w850w952w1153w1254w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
24 touches
66 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xcf61f287…3f4e
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0002
0xf5b5f7…6d70
8 touches
6 conflicts
0xfcb7b8b2…ebb3
0x065c9d…c394
8 touches
6 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
66 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity