← previous blocknext block →recent activity
Analyzing
Block #100,134,934
31 transactions · 30 stateful · 2026-08-29 08:19:41 UTC
Parallelism
68/100
Blocked
43%
Avg conflicts / tx
1.74
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #100,134,934 · 31 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
1w02w05w17w08w110w212w313w415w516w618w721w123w830w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xfb14d7f1…e509
0x34b655…2a6f
12 touches
15 conflicts
0x77ed546f…a357
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6426
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xb54c8ced…5b8c
0x34b655…2a6f
8 touches
6 conflicts
0x53c0fef6…250b
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
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
28 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity