← previous blocknext block →recent activity
Analyzing
Block #100,809,198
51 transactions · 39 stateful · 2026-08-31 16:56:14 UTC
Parallelism
67/100
Blocked
79%
Avg conflicts / tx
2.63
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #100,809,198 · 51 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
1w04w15w26w07w19w210w012w113w014w115w130w231w332w233w334w335w436w538w439w541w745w1147w1350w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
26 touches
78 conflicts
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0x482471ad…122f
0x34b655…2a6f
18 touches
36 conflicts
0xb409e204…89ac
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0x40c49f…2af0
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x886db264…846e
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 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
78 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity