← previous blocknext block →recent activity
Analyzing
Block #100,233,123
37 transactions · 23 stateful · 2026-08-29 16:34:06 UTC
Parallelism
84/100
Blocked
65%
Avg conflicts / tx
0.92
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,233,123 · 37 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w37w08w09w110w212w314w425w426w528w133w135w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0x46279ae7…20dd
0x2b46c0…1669
6 touches
3 conflicts
0x53e50026…6d8c
0x2b46c0…1669
6 touches
3 conflicts
0x6eff310a…c34c
0x2b46c0…1669
6 touches
3 conflicts
0x7f4a8466…f2cc
0x2b46c0…1669
6 touches
3 conflicts
0xe49b1b9b…0be1
0x2b46c0…1669
6 touches
3 conflicts
0x482471ad…122f
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity