← previous blocknext block →recent activity
Analyzing
Block #106,954,055
24 transactions · 22 stateful · 2026-09-22 05:39:49 UTC
Parallelism
79/100
Blocked
32%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,954,055 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w07w08w111w112w213w314w417w118w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x574628e9…dcc3
0x34b655…2a6f
10 touches
10 conflicts
0xa1a7a0b3…855f
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xfc906557…ae7f
0x34b655…2a6f
6 touches
3 conflicts
0x1d81790c…b9f7
0x34b655…2a6f
4 touches
1 conflict
0x3643741b…109c
0x34b655…2a6f
4 touches
1 conflict
0x4a31a1e5…f90a
0x34b655…2a6f
4 touches
1 conflict
0x62d6e82b…a750
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
10 conflicts on slot 0x574628e919…e4dcc3
Audit this contract →
← previous block·next block →recent activity