← previous blocknext block →recent activity
Analyzing
Block #100,137,090
20 transactions · 18 stateful · 2026-08-29 08:30:41 UTC
Parallelism
60/100
Blocked
44%
Avg conflicts / tx
1.35
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,137,090 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w010w111w212w313w416w517w618w719w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2cfe7c05…2b42
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x50c61506…343f
0x34b655…2a6f
8 touches
6 conflicts
0x0b0611f7…e63a
0x34b655…2a6f
6 touches
3 conflicts
0x327c57dd…836d
0x34b655…2a6f
6 touches
3 conflicts
0x4fce3905…6f4f
0x34b655…2a6f
6 touches
3 conflicts
0x61e2c349…73aa
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
15 conflicts on slot 0x2cfe7c0595…832b42
Audit this contract →
← previous block·next block →recent activity