← previous blocknext block →recent activity
Analyzing
Block #106,931,134
32 transactions · 30 stateful · 2026-09-22 03:44:27 UTC
Parallelism
53/100
Blocked
67%
Avg conflicts / tx
2.94
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #106,931,134 · 32 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
1w02w13w24w35w46w211w212w313w414w515w616w717w818w119w920w1021w1122w1228w1329w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x810a3aa2…0227
0x34b655…2a6f
20 touches
45 conflicts
0xba1edffb…323e
0x34b655…2a6f
16 touches
28 conflicts
0x42522e76…2592
0x34b655…2a6f
14 touches
21 conflicts
0xb6a59002…65eb
0x34b655…2a6f
14 touches
21 conflicts
0xd125c3f8…99aa
0x34b655…2a6f
12 touches
15 conflicts
0x04f373b3…8072
0x34b655…2a6f
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0xe720a4c6…8eb0
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
45 conflicts on slot 0x810a3aa264…c40227
Audit this contract →
← previous block·next block →recent activity