← previous blocknext block →recent activity
Analyzing
Block #106,585,942
40 transactions · 34 stateful · 2026-09-20 22:46:02 UTC
Parallelism
63/100
Blocked
65%
Avg conflicts / tx
1.95
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #106,585,942 · 40 txs across 15 waves · depth 15
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
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w07w18w110w011w112w013w114w115w219w221w323w426w427w529w730w832w1035w1039w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb654bd89…a83b
0x34b655…2a6f
16 touches
28 conflicts
0x8c908b22…9452
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x6b23a89e…1057
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 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 0xb654bd89ad…dba83b
Audit this contract →
← previous block·next block →recent activity