← previous blocknext block →recent activity
Analyzing
Block #106,916,516
34 transactions · 33 stateful · 2026-09-22 02:30:52 UTC
Parallelism
56/100
Blocked
73%
Avg conflicts / tx
2.32
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #106,916,516 · 34 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
1w02w13w24w35w36w47w18w111w012w113w214w315w416w518w619w720w821w922w1023w1124w1225w1326w1431w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53ca1284…cb2c
0x34b655…2a6f
20 touches
45 conflicts
0xccebf5c5…8758
0x34b655…2a6f
18 touches
36 conflicts
0xf782ee27…41cd
0x34b655…2a6f
18 touches
36 conflicts
0x51087f5a…61f7
0x34b655…2a6f
14 touches
21 conflicts
0x803d32b5…8094
0x34b655…2a6f
12 touches
15 conflicts
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
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
45 conflicts on slot 0x53ca128412…cacb2c
Audit this contract →
← previous block·next block →recent activity