← previous blocknext block →recent activity
Analyzing
Block #106,916,422
26 transactions · 25 stateful · 2026-09-22 02:30:24 UTC
Parallelism
58/100
Blocked
52%
Avg conflicts / tx
1.31
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,916,422 · 26 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w07w19w010w111w212w313w414w515w616w717w818w919w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51087f5a…61f7
0x34b655…2a6f
12 touches
15 conflicts
0xccebf5c5…8758
0x34b655…2a6f
12 touches
15 conflicts
0xe5eb3c33…0e3a
0x34b655…2a6f
12 touches
15 conflicts
0x8469771e…1c75
0x34b655…2a6f
12 touches
15 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x803d32b5…8094
0x34b655…2a6f
10 touches
10 conflicts
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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
15 conflicts on slot 0x51087f5abf…f061f7
Audit this contract →
← previous block·next block →recent activity