← previous blocknext block →recent activity
Analyzing
Block #106,188,123
35 transactions · 32 stateful · 2026-09-19 13:23:49 UTC
Parallelism
60/100
Blocked
66%
Avg conflicts / tx
2.46
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #106,188,123 · 35 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w17w211w312w416w418w519w620w721w822w923w1024w925w1126w1227w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a29c64d…e772
0x34b655…2a6f
18 touches
36 conflicts
0x82fd45e4…0935
0x34b655…2a6f
12 touches
15 conflicts
0xfefb0189…f726
0x34b655…2a6f
12 touches
15 conflicts
0x35b89cd8…5092
0x34b655…2a6f
10 touches
10 conflicts
0xf788c790…e66f
0x34b655…2a6f
10 touches
10 conflicts
0xd41f5136…97c6
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x159cff26…7665
0x34b655…2a6f
10 touches
10 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
36 conflicts on slot 0x1a29c64dd8…e6e772
Audit this contract →
← previous block·next block →recent activity