← previous blocknext block →recent activity
Analyzing
Block #106,100,339
17 transactions · 16 stateful · 2026-09-19 06:02:01 UTC
Parallelism
59/100
Blocked
50%
Avg conflicts / tx
1.47
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,100,339 · 17 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
1w02w13w04w15w26w37w413w014w215w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcfe180d7…b5a4
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xa9a49465…0424
0x34b655…2a6f
6 touches
3 conflicts
0xae522ec4…d1e5
0x34b655…2a6f
6 touches
3 conflicts
0xb13b96bd…a3cb
0x34b655…2a6f
6 touches
3 conflicts
0xb1482e4f…6af9
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
10 conflicts on slot 0xcfe180d7a8…3db5a4
Audit this contract →
← previous block·next block →recent activity