← previous blocknext block →recent activity
Analyzing
Block #106,216,058
32 transactions · 29 stateful · 2026-09-19 15:44:27 UTC
Parallelism
69/100
Blocked
45%
Avg conflicts / tx
1.53
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,216,058 · 32 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w011w012w113w014w115w217w319w120w421w522w623w730w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xecf22f58…5939
0x34b655…2a6f
16 touches
28 conflicts
0x67cb0bae…52c3
0x34b655…2a6f
14 touches
21 conflicts
0xd6d040d9…9ae3
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xfe39a1f7…8eb0
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x2c797f96…9b99
0x34b655…2a6f
6 touches
3 conflicts
0xd29e547b…a1dd
0x34b655…2a6f
6 touches
3 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 0xecf22f58ca…2c5939
Audit this contract →
← previous block·next block →recent activity