← previous blocknext block →recent activity
Analyzing
Block #106,932,409
37 transactions · 36 stateful · 2026-09-22 03:50:52 UTC
Parallelism
65/100
Blocked
72%
Avg conflicts / tx
2.54
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #106,932,409 · 37 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w47w48w010w011w112w213w314w415w516w617w318w419w127w428w532w633w736w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd1b40f29…9b9d
0x34b655…2a6f
18 touches
36 conflicts
0xb7aa9720…56df
0x34b655…2a6f
16 touches
28 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
16 touches
28 conflicts
0x9375a764…dca1
0x34b655…2a6f
16 touches
28 conflicts
0x503df629…59cb
0x34b655…2a6f
14 touches
21 conflicts
0x42522e76…2592
0x34b655…2a6f
14 touches
21 conflicts
0x1260550f…1a38
0x34b655…2a6f
12 touches
15 conflicts
0x3e163287…f328
0x34b655…2a6f
10 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 0xd1b40f2924…ae9b9d
Audit this contract →
← previous block·next block →recent activity