← previous blocknext block →recent activity
Analyzing
Block #106,932,160
27 transactions · 26 stateful · 2026-09-22 03:49:36 UTC
Parallelism
59/100
Blocked
77%
Avg conflicts / tx
2.7
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,932,160 · 27 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w59w610w711w524w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70986451…c6bd
0x34b655…2a6f
16 touches
28 conflicts
0xb7c91a18…03ca
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…001d
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…002d
0x1b6862…e19c
14 touches
21 conflicts
0x17a7f697…dcb6
0x1b6862…e19c
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0x251ee419…4404
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 0x7098645134…3ac6bd
Audit this contract →
← previous block·next block →recent activity