← previous blocknext block →recent activity
Analyzing
Block #106,215,914
23 transactions · 20 stateful · 2026-09-19 15:43:43 UTC
Parallelism
65/100
Blocked
55%
Avg conflicts / tx
1.39
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,215,914 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w110w213w314w415w116w517w618w721w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x103e56ba…1139
0x34b655…2a6f
14 touches
21 conflicts
0xb7af7ea3…7d7d
0x34b655…2a6f
12 touches
15 conflicts
0xe030119e…291e
0x34b655…2a6f
10 touches
10 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
10 touches
10 conflicts
0xfbabb02d…af07
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xab981df1…2941
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
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
21 conflicts on slot 0x103e56bab1…071139
Audit this contract →
← previous block·next block →recent activity