← previous blocknext block →recent activity
Analyzing
Block #106,576,912
37 transactions · 35 stateful · 2026-09-20 22:00:35 UTC
Parallelism
68/100
Blocked
74%
Avg conflicts / tx
2.84
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #106,576,912 · 37 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w07w08w110w111w214w115w216w221w522w623w724w826w1027w1133w534w636w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41bd981d…559d
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xdbb571e4…6829
0x34b655…2a6f
12 touches
15 conflicts
0xcc844ab5…4c6d
0x34b655…2a6f
10 touches
10 conflicts
0xe5eb3c33…0e3a
0x34b655…2a6f
10 touches
10 conflicts
0x4be9812b…48a9
0x34b655…2a6f
10 touches
10 conflicts
0xd4d5a903…c8d2
0xd32edf…ff58
9 touches
10 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
36 conflicts on slot 0x41bd981d9a…89559d
Audit this contract →
← previous block·next block →recent activity