← previous blocknext block →recent activity
Analyzing
Block #106,930,627
61 transactions · 56 stateful · 2026-09-22 03:41:54 UTC
Parallelism
72/100
Blocked
79%
Avg conflicts / tx
3.33
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #106,930,627 · 61 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w713w514w615w745w852w957w1359w1560w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc844ab5…4c6d
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x46483cb1…e7ca
0x34b655…2a6f
16 touches
28 conflicts
0x4a5be785…2a66
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…002d
0x1b6862…e19c
14 touches
21 conflicts
0xb0e4f69d…34e6
0x1b6862…e19c
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0x14fab3c8…40d9
0x34b655…2a6f
14 touches
21 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 0xcc844ab542…814c6d
Audit this contract →
← previous block·next block →recent activity