← previous blocknext block →recent activity
Analyzing
Block #100,230,128
26 transactions · 25 stateful · 2026-08-29 16:19:01 UTC
Parallelism
73/100
Blocked
52%
Avg conflicts / tx
1.23
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,230,128 · 26 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w05w06w18w09w110w212w113w214w315w416w517w218w624w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x72803786…baf3
0x34b655…2a6f
12 touches
15 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xec162e6c…be77
0x34b655…2a6f
10 touches
10 conflicts
0x29cd05f5…390c
0x34b655…2a6f
8 touches
6 conflicts
0x15698ac9…2a46
0x34b655…2a6f
6 touches
3 conflicts
0x10a5a231…be40
0x34b655…2a6f
6 touches
3 conflicts
0xc7954a60…d294
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 0x728037862f…28baf3
Audit this contract →
← previous block·next block →recent activity