← previous blocknext block →recent activity
Analyzing
Block #106,199,455
23 transactions · 22 stateful · 2026-09-19 14:20:50 UTC
Parallelism
61/100
Blocked
55%
Avg conflicts / tx
2.48
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,199,455 · 23 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w06w17w28w310w211w313w314w415w516w617w718w822w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6827790…2867
0x34b655…2a6f
16 touches
28 conflicts
0x7cf3eb0f…06c5
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xf47769ab…0d08
0x34b655…2a6f
6 touches
3 conflicts
0x10473e4f…cf84
0x34b655…2a6f
6 touches
3 conflicts
0x35b89cd8…5092
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
28 conflicts on slot 0xa68277909c…252867
Audit this contract →
← previous block·next block →recent activity