← previous blocknext block →recent activity
Analyzing
Block #106,403,072
17 transactions · 17 stateful · 2026-09-20 07:25:38 UTC
Parallelism
53/100
Blocked
59%
Avg conflicts / tx
2.18
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,403,072 · 17 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
1w02w13w25w28w39w410w512w513w614w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfdd131fa…dbdb
0x34b655…2a6f
14 touches
21 conflicts
0xc20bb2f9…b221
0x34b655…2a6f
12 touches
15 conflicts
0xc412a0b2…b15f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x30ceaa11…f481
0x34b655…2a6f
10 touches
10 conflicts
0x6af2981e…5a35
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
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 0xfdd131fae1…f8dbdb
Audit this contract →
← previous block·next block →recent activity