← previous blocknext block →recent activity
Analyzing
Block #106,565,212
44 transactions · 39 stateful · 2026-09-20 21:01:42 UTC
Parallelism
70/100
Blocked
44%
Avg conflicts / tx
1.73
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #106,565,212 · 44 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
9w010w112w013w215w317w418w519w620w721w822w923w924w1025w1126w1240w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d99a6e0…be0e
0x34b655…2a6f
18 touches
36 conflicts
0x86cea35b…bdff
0x34b655…2a6f
12 touches
15 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
12 touches
15 conflicts
0xbaf6ed88…c179
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x810a3aa2…0227
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x0de7749d…5bef
0x34b655…2a6f
8 touches
6 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 0x5d99a6e0f3…62be0e
Audit this contract →
← previous block·next block →recent activity