← previous blocknext block →recent activity
Analyzing
Block #106,206,829
32 transactions · 26 stateful · 2026-09-19 14:57:59 UTC
Parallelism
66/100
Blocked
62%
Avg conflicts / tx
1.13
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,206,829 · 32 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w09w010w313w114w216w318w421w523w525w629w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x839c0c71…bada
0x34b655…2a6f
8 touches
6 conflicts
0x085df2c1…305a
0x34b655…2a6f
6 touches
3 conflicts
0x20571ffc…1654
0x34b655…2a6f
6 touches
3 conflicts
0x26e65290…f011
0x34b655…2a6f
6 touches
3 conflicts
0x3643741b…109c
0x34b655…2a6f
6 touches
3 conflicts
0x68292fe7…d918
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