← previous blocknext block →recent activity
Analyzing
Block #106,199,061
29 transactions · 26 stateful · 2026-09-19 14:18:51 UTC
Parallelism
66/100
Blocked
54%
Avg conflicts / tx
1.9
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,199,061 · 29 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w05w110w111w212w114w316w417w418w519w620w721w822w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x411b6473…3740
0x34b655…2a6f
18 touches
36 conflicts
0x5717771c…45ed
0x34b655…2a6f
14 touches
21 conflicts
0x24ed74ea…a3ff
0x34b655…2a6f
10 touches
10 conflicts
0xac0b4a08…faae
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x92b49f44…ee4f
0x34b655…2a6f
8 touches
6 conflicts
0x2183420b…ec6a
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 0x411b647303…d23740
Audit this contract →
← previous block·next block →recent activity