← previous blocknext block →recent activity
Analyzing
Block #106,556,172
24 transactions · 23 stateful · 2026-09-20 20:16:12 UTC
Parallelism
67/100
Blocked
48%
Avg conflicts / tx
1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,556,172 · 24 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
1w02w13w24w35w36w48w010w112w013w118w519w622w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x735a86cd…b64d
0x34b655…2a6f
8 touches
6 conflicts
0xd7793452…ae6a
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x4beaf610…8a09
0x34b655…2a6f
6 touches
3 conflicts
0xb2560305…f27d
0x34b655…2a6f
6 touches
3 conflicts
0xdbf974a4…b232
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
6 conflicts on slot 0x735a86cd19…53b64d
Audit this contract →
← previous block·next block →recent activity