← previous blocknext block →recent activity
Analyzing
Block #106,110,182
24 transactions · 21 stateful · 2026-09-19 06:51:33 UTC
Parallelism
58/100
Blocked
48%
Avg conflicts / tx
1.21
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,110,182 · 24 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w39w112w413w516w617w718w820w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdfc7e6c9…04c2
0x34b655…2a6f
10 touches
10 conflicts
0xac1228d4…f289
0x34b655…2a6f
10 touches
10 conflicts
0x2a2896a0…2a0a
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x7462b8f2…6312
0x34b655…2a6f
8 touches
6 conflicts
0xba1edffb…323e
0x34b655…2a6f
6 touches
3 conflicts
0xab981df1…2941
0x34b655…2a6f
6 touches
3 conflicts
0xbb7c4b5c…6304
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 0xdfc7e6c987…4704c2
Audit this contract →
← previous block·next block →recent activity