← previous blocknext block →recent activity
Analyzing
Block #106,916,069
41 transactions · 38 stateful · 2026-09-22 02:28:37 UTC
Parallelism
66/100
Blocked
66%
Avg conflicts / tx
1.85
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #106,916,069 · 41 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w07w18w310w011w114w015w116w217w318w419w520w121w629w232w134w239w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x158cd73a…d47b
0x34b655…2a6f
16 touches
28 conflicts
0xb5c7c6aa…fdba
0x34b655…2a6f
16 touches
28 conflicts
0x6c60fbcf…8744
0x34b655…2a6f
16 touches
28 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
16 touches
28 conflicts
0xe6a595bf…3c45
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
0x34b655…2a6f
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
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
28 conflicts on slot 0x158cd73a84…69d47b
Audit this contract →
← previous block·next block →recent activity