← previous blocknext block →recent activity
Analyzing
Block #106,468,066
22 transactions · 21 stateful · 2026-09-20 12:52:47 UTC
Parallelism
64/100
Blocked
48%
Avg conflicts / tx
1.41
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,468,066 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w18w011w213w014w315w416w117w418w519w620w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef948c34…0463
0x34b655…2a6f
14 touches
21 conflicts
0xfdd131fa…dbdb
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x159cff26…7665
0x34b655…2a6f
8 touches
6 conflicts
0x4118bd12…924a
0x34b655…2a6f
8 touches
6 conflicts
0xf51ddc84…51c6
0x34b655…2a6f
8 touches
6 conflicts
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x88e771e8…7d4a
0x34b655…2a6f
4 touches
1 conflict
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
21 conflicts on slot 0xef948c34d4…960463
Audit this contract →
← previous block·next block →recent activity