← previous blocknext block →recent activity
Analyzing
Block #106,381,500
25 transactions · 23 stateful · 2026-09-20 05:37:04 UTC
Parallelism
56/100
Blocked
48%
Avg conflicts / tx
1.96
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,381,500 · 25 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
1w03w14w05w111w212w313w417w518w619w721w822w923w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd9ba26b…108d
0x34b655…2a6f
18 touches
36 conflicts
0x7cee389f…adef
0x34b655…2a6f
18 touches
36 conflicts
0xe8058ec4…ebac
0x34b655…2a6f
10 touches
10 conflicts
0xfbc95f8d…95ab
0x34b655…2a6f
10 touches
10 conflicts
0x3e6302c8…64f5
0x34b655…2a6f
8 touches
6 conflicts
0xee776f86…e198
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 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 0xcd9ba26bf8…62108d
Audit this contract →
← previous block·next block →recent activity