← previous blocknext block →recent activity
Analyzing
Block #106,931,560
41 transactions · 40 stateful · 2026-09-22 03:46:35 UTC
Parallelism
51/100
Blocked
75%
Avg conflicts / tx
2.78
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #106,931,560 · 41 txs across 20 waves · depth 20
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
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w412w413w514w615w716w817w918w1019w1120w521w1229w634w435w738w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x155e52ca…fac7
0x34b655…2a6f
20 touches
45 conflicts
0x469dac8d…3411
0x34b655…2a6f
18 touches
36 conflicts
0x3740f434…cccb
0x34b655…2a6f
16 touches
28 conflicts
0x66511956…e9dc
0x34b655…2a6f
16 touches
28 conflicts
0x42522e76…2592
0x34b655…2a6f
16 touches
28 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
16 touches
28 conflicts
0x7ddef8d6…636b
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
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
45 conflicts on slot 0x155e52cae2…d8fac7
Audit this contract →
← previous block·next block →recent activity